Develop Bugs

[Q] Stuck in Clockwork Mod Bootloop

Installed Andromadus 4.0 beta on my wife's G2. When I got home from work my wife said that the phone had restarted and would now only boot into clockworkmod recovery v5.8.1.0. Tried factory reset and wiping the caches and reflashing. Also tried flashing CM9 unofficial but the phone just shuts off in the middle of the flash and reboots back into clockwork. Tried to flash stockmod but I get a "can't open error". Currently the phone boots into Clockwork mod, stays on for 60 secs, then reboots itself back into clockwork mod. Help please!

maybe try to reflash your recovery, boot into fastboot and try...

When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer

Nipqer said:
When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer
Click to expand...
Click to collapse
Well that must be why that option didn't work. I'm pretty new to all this. Have a MyTouch I rooted a couple weeks ago that works great. But I am having fits with this one, and worse, it's my wifes phone Any other suggestions?

wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium

demkantor said:
wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
It worked! Thank you so much!

great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit

Not really working!
demkantor said:
great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit
Click to expand...
Click to collapse
I tried installing superwipe, and all sorts of different android operating systems but I cant seem to get my phone to get out of clockworkmod v5.8.1.0 and I can get to fastboot or hboot but it wont go passed the HTC screen. Every time I try installing an updated OS or a different OS or even doing the superwipe.zip it just says installation aborted and i can't get it to work! Any tips?

For future reference, don't go blindly flashing "Stock" images and such via the bootloader you tend to get yourself into more trouble that way (bricking, or making it difficult to get back to rooting).
Also if you're frequently using ICS roms I recommend using 4EXT Touch Recovery instead of ClockworkMod. A lot more useful tools in the recovery itself especially for wiping or formatting specific partitions.
When you get a chance check out which eMMC is used on that phone (click the eMMC name in my signature to see the poll thread which tells you how to check). Good for future reference if something acts up again.

rooting and rom-ing this piece.

i have a droid x2 that i have rooted and switched roms on numerous times, as well as sbfing becoming one of my close friends. not sure what to do with the 3 different pages on rooting applications and methods. does a link to actual step by step instructions on how to root and intall roms exist? last night i rooted and installed twrp using the utility, but could not get it to boot for anything. held power down and all i get is a normal boot . when i went to install AOKP , i used the utility to get into twrp RIGHT after putting FFF on it. i flashed the rom and gapps after wiping data, and i got a blank screen for an hour. i found a tutorial on mounting sd card through twrp and saved it. my question is what is the proper way to root 6.2.2? and will installing roms through working twrp actualy work? if so how do i get twrp to work? thanks in advance guys.

clarity
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol

I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium

Lorenzo VonMatterhorn said:
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
Click to expand...
Click to collapse
Yes, you use adb but it instructs you what to type.
Sent from my Galaxy Nexus using xda premium

pyroscott said:
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.

Yes the first step should be root... which in my case also installs twrp...

If you're planning to install a custom ROM, there's no point in rooting. FFF and TWRP are more than enough.

aokp
ok well i rooted. and now twrp works flawlessly. but when i try to flash aokp, i wipe data/factory reset, install aokp and then gapps, i get nothing but a black screen after rebooting. after waiting a minute or two, i rebooted into recovery and restored a backup. am i doing something wrong? i started on 6.2.2 if that helps at all.

You should -always- wipe cache and dalvik-cache when flashing ROMs.
When you're upgrading the same ROM from a lower version to a newer one (for example, going from gede 1.65 to 1.7) you may skip factory reset, so long as there isn't a major change (going from normal to linaro, for example).
However, it is good practice to let Titanium Backup handle all of your /data backups and just factory reset every time as well.

You have the two most important steps done.
1. You have TWRP installed and you can boot into it. That is one of the hardest steps it appears.
2. You did a backup before doing anything else.
As Dasanko said you also need to wipe cache and dalvik-cache. When I do a new rom I wipe data, system, cache and dalvik-cache.
Titanium Backup (TiBu) is also awesome to restore your apps. However, you will need to install TiBu to use it to restore other apps. Some ROMS have it installed already and some don't. If you don't have access to TiBu from the Rom your are flashing you will need the GApps installed to get the Play Store. You can then download TiBu be able to restore your chosen apps.

Lorenzo VonMatterhorn said:
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Click to expand...
Click to collapse
Yes, you should get the screen with the triangle. I would try flashing the recovery again
Sent from my Galaxy Nexus using xda premium

also when you are installing a new rom I always wipe system so you dont have any errors because that is where the old rom is located. btw cm9 and aokp are both really nice on this device

[Q] Miui Unstable, constant reboots, cannot flash

Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.

Does anyone know what would cause the phone to keep restoring its previous state ? As I mentioned I have looked for the recovery-from-boot script and cannot find it. Thanks!
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse

I have attached the output I get from logcat. Please help!
***Removed logcat file***

1) did you wipe data/cache when you switched roms?
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.

Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do

Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus

cdexsw said:
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.

Dr01d4l1f3 said:
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Click to expand...
Click to collapse
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus

eqjunkie829,
Is it lonely up there on your high horse ? This is not the first time or the first phone I have rooted.
eqjunkie829 said:
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Click to expand...
Click to collapse

cdexsw,
Thanks for the tip, I will try that.
cdexsw said:
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
Click to expand...
Click to collapse

Zepius said:
2) dont use odin, its not really supported for thisany phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Odin is a leaked tool from Sammy, it is not supported on any device.
OP, read efrant's guide on flashing stock (sticky, general section)
Sent from my i9250

[Q] How to go from 4.0.3 Jedi Mind Trick to Cyanogenmod 10.0.0 Stable Release

Hello all just bought a new Samsung Galaxy SII from craigslist already rooted with 4.0.3 Jedi Mind Trick. After reading for what seems 4-5 hours i have been trying to put together how to properly without bricking switching it to 10.0.0 Stable as i use to use Cyanogenmod 2-3 years ago on my devices. Seem alot of things have changed and there is a cluster**** of stuff out there now. If you could direct me to a how to or show me how to do it i would greatly appreciate it!
Thanks all!

Assuming you have nothing personal to back up that you can't just download from google play or your google account again: download cyanogen 10 and it's gapps. reboot into recovery mode. factory reset, wipe data, wipe system, wipe cache, wipe dalvik. pick the install zip from sd card or so option, browse to cyanogen, then install gapps the same way. wipe dalvik again and reboot.

I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.

Alawishis said:
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Click to expand...
Click to collapse
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?

melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.

new ion? said:
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
Click to expand...
Click to collapse
trying to look up how to do that now .... Searching the forum now... Might you be able to tell me real quick how? I already Downloaded the 5.2 file they suggest to use but can't find a working toturial that is just for flashing the cwm.

melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.

arcsine said:
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
Click to expand...
Click to collapse
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-

melvinator said:
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
Click to expand...
Click to collapse
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium

new ion? said:
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.

melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
Go back, format system, and then reinstall.
Sent from my SAMSUNG-SGH-T989 using xda premium

Update your recovery to twrp or cwm 6+ and don't use dark side scripts
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Please excuse my harshness but this is not as hard as many make it seem. I would say if it takes you more than a couple attempts maybe it is just not for you. I only say this because I would hate to see you mess up your phone. Now if you think a bootloop is a brick then we need to do things at a slower pace with you.
If you already have your phone rooted then
1.download goomanager from the playstore and then
2.open it up and allow it to grant permission from CM
3.hit menu button while goo manager is open
4.click on install OpenRecoveryScript
5.let it do its thing
6.reboot into your new TWRP recovery
7.Wipe/Data Factory Reset
8.Flash Rom
9.Flash Gapps
10.Reboot
You can throw in a backup of files somewhere in there if you like.... Your choice

melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
I had a bootloop when using CWM v6.0.1.5. So a friend of mine told me he had success with CWM v6.0.1.5 Touch. So I switched to the touch recovery and... SUCCESS.
Here's the link to CWM touch and non-touch:
http://forum.xda-developers.com/showthread.php?t=1893464

A boot loop could mean a bad download or bad flash but it is most definitely NOT a bricked device. All you needed to do was get a fresh download and move it to your SD card by mounting it in recovery. Then, wipe EVERYTHING but the SD. EVERYTHING. Then flash the ROM, Gapps and whatever radio. I go from CM to AOKP to other random TW roms all the time and never have issues.

The 2 best recoveries are twrp or my favorite because I'm used to it is cwm 6.0.1.5. http://forum.xda-developers.com/showthread.php?t=1844637
Also if your phone boot loops don't freak out' just either reboot to see if that works out first and if not reboot into recovery. Also with these new recoveries do not use dark side scripts.
Factory reset
Format system
Format cache
Format data
Flash ROM
Flash gapps
Reboot and enjoy
Sent from my SAMSUNG-SGH-T989 using xda premium

This did it!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Sorry for the necro on the thread, but I didn't want it to be stated I didn't look around some either.
I am going from JMT to CM and want to make sure it's as seamless as possible. I use CWM and usually usually use darkside complete wipes, but I read in a previous post not to use darkside. Is there a reason for this? I can't see why this wouldn't work as it's just a wipe.
Also I use Titanium Backup. Is it possible to backup my apps and data and restore them since its not TW any longer? I want to be able to restore as much of my data as possible and make sure I don't lose it.
P.S. - If thread necroing is not appreciated, I apologize.

GNEX frozen at JB startup animation (multicolored X)

Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing

Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app

This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app

berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app

As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app

Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info

Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse

small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse

installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...

had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?

went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse

Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse