Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by kendon

  1. i am a unix admin so i know what this command actually does. i would consider it safe. i rarely wipe my phones, so i havent used it.
  2. i believe it was inside a branch. i got the nexus from telekom (former t-mobile) here in germany, i didn't check before unlocking and flashing.
  3. updated bootloader and radio twice by now, never had a problem. rom just booted up and was fine.
  4. nope. flashing of the bootloader does exactly that, flashing of the bootloader. as does radio, and recovery fwiw.
  5. use the command like this: adb shell rm -fr /data/media/* then you should be fine. don't forget to mount "data" in cwm menu before.
  6. for future reference (if someone ever uses the search...) you could have also used adb. boot to recovery, then: adb shell mount /data adb push ROMFILE.zip /sdcard/
  7. nope. but tbh i dont think it is of much interest, so...
  8. radios are widely available on the net, as are bootloaders. what version of the bootloader do you have?
  9. 1. check system/build.prop 2. yes, if they work you can put them in the rom from the beginning 3. yes, be sure to know what you delete (or don't whine when it doesn't work afterwards :))
  10. you f*ed up the zip file. check md5s, they wont match. make that zip again, clear your sdcard, try again.
  11. come on kids, that is (like he said) the stock recovery image every freakin' android phone has. this is how original ota updates are applied. obviously ota updates are signed with a zte key (or provider, not exactly sure), and as long as no one manages to get such a key it is pretty much worthless to us (sure on that one). now move along, nothing to see here...
  12. you can also use 'logcat' in a terminal, i.e. 'logcat -f /sdcard/logcat.txt'. keep in mind there are three logcat buffers, i'd create a script like this: #!/system/bin/sh /system/bin/logcat -b main -f /sdcard/logcat.main.txt & /system/bin/logcat -b radio -f /sdcard/logcat.radio.txt & /system/bin/logcat -b events -f /sdcard/logcat.events.txt furthermore some kernel messages might be interesting, not exactly sure where to look tho. in case of reboot probably /proc/last_kmsg (after the reboot).
  13. the task here is to modify the ramdisk to support init.d scripts. same results here with lzma, not working. are we sure that split_bootimg does its job correctly?
  14. the link to split_bootimage is dead, however i got it on my laptop: [email protected]:~/Desktop/Swedish_Spring_RLS4b$ split_bootimg.pl boot-gen1.img Page size: 2048 (0x00000800) Kernel size: 3242164 (0x003178b4) Ramdisk size: 113808 (0x0001bc90) Second size: 0 (0x00000000) Board name: Command line: Writing boot-gen1.img-kernel ... complete. Writing boot-gen1.img-ramdisk.gz ... complete. [email protected]:~/Desktop/Swedish_Spring_RLS4b$ gunzip -c boot-gen1.img-ramdisk.gz | cpio -i gzip: boot-gen1.img-ramdisk.gz: not in gzip format cpio: premature end of archive it extracts something, but no archive (second line to show how 'file' output would look like for an actual archive): [email protected]:~/Desktop/Swedish_Spring_RLS4b$ file boot-gen1.img-ramdisk.gz boot-gen1.img-ramdisk.gz: data [email protected]:~/Desktop/Swedish_Spring_RLS4b$ file ../Swedish_Spring_RLS4b.zip ../Swedish_Spring_RLS4b.zip: Zip archive data, at least v2.0 to extract edit: very same happens for gen2 btw.
  15. no it won't... $ unpack-bootimg.pl boot.img Could not find any embedded ramdisk images. Are you sure this is a full boot image?
  16. http://forum.xda-developers.com/showthread.php?t=905003 ?
  17. not particularly, but i am generaly interested in all modding and porting, so...
  18. yes, and the title implies that they are the same, so it could be misleading to newbies. the thread suggest that exactly this misunderstanding may lead to a bricked device.
  19. so maybe you wanna edit that misleading thread title now?
  20. http://forum.xda-developers.com/showthread.php?t=857537 there is a tool for that.
  21. saying "not available" is missleading. the correct wording would be "locked" or "secured" or anything in that direction. it can generally be unlocked, depends on the phone modell whether a procedure is available or not.
  22. usb debugging enabled? settings -> applications
  23. i don't know of any official statement from paul regarding this topic (more than the one about future support he puts in every rom post now), but here is what i suppose: paul concentrates on the basic stuff like the initial rooting, making rooting feasible for newbies, and providing a significantly improved version of the stock roms, usually including a tweaked kernel. there is more than enough work involved in that for one person, or even for a small team. be grateful for the effort paul puts into his work to provide awesome tools like visionary, porting the clockworkmod to rooted devices and last but not least providing this forum as a platform for newbies that want more from their devices (videowalkthroughs for rooting, step-by-step instructions etc). there is no obligation to pay for anything, all the necessary tools are freely available for registered users. if you want to go deeper into the world of custom roms, modding and developing go to places like xda-developers.com or the super awesome villainrom.co.uk (:(). having made some roms myself i can tell you that everything beyond the standard improving of a stock rom goes into very time-consuming little details, and is hard to manage for more than one or two roms for a maximum of two different devices. look at the device list here at the forum and you'll see the point. for a not too small number of these paul has provided the first method of rooting, and eventually userfriendly tools to do the job for you. if you'd understand the processes (and risks!) of the stuff that i.e. visionary does on a dhd to release its full potential to the user you'd gladly pay five bucks for the app alone. at first i was disappointed as you were, but thinking about it it makes sense, and pauls contribution to the android scene are still among the most important ones at all, as will be the coming ones. not a fanboy here, just saying don't forget the big picture.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.