Database Info

[Q] Unable to flash roms(have root)

Yes can someone plz help me i just rooted my nexus using the pdanet method. For some reason when i try to reboot in to recovery using rom manager i get that yellow tranagle i cant flash anything but i have root. any ideas and whats going wrong and how to fix this

Go into rom manager and reflash clockworkmod! that usually does the trick
Sent from my Nexus S using XDA Premium App

Ok tried that and it worked but the two roms i tried wont boot its like there stuck it just keeps looping any ideas on that

whitetiger2429 said:
Ok tried that and it worked but the two roms i tried wont boot its like there stuck it just keeps looping any ideas on that
Click to expand...
Click to collapse
because you need to wipe(factory reset) when flashing different roms. when you upgrade the same rom, you dont have to wipe.

i have and its still not working do i need to wipe cahce to

whitetiger2429 said:
i have and its still not working do i need to wipe cahce to
Click to expand...
Click to collapse
wiping data(factory reset) should take care of that. wipe, flash rom, flash gapps(if needed), and reboot. thats all.

done all that still gets stuck at the loading screen

ok got one to flash i did a cache wipe to and it seem to work ty

whitetiger2429 said:
Yes can someone plz help me i just rooted my nexus using the pdanet method. For some reason when i try to reboot in to recovery using rom manager i get that yellow tranagle i cant flash anything but i have root. any ideas and whats going wrong and how to fix this
Click to expand...
Click to collapse
I'm not sure why, but sometimes when I flash a recovery and reboot into recovery from ROM Manager, I get the same thing. But if I flash, then power off and boot into recovery using volume+powerUp, it works fine.

[Q] Blank screen after Nandroid Restore

I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.

anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?

anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically

jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?

So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?

anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app

Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)

Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app

Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!

Running mastamoon's unofficial CM 10.1. =)

anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app

Trouble getting Miui to boot....again

Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated

avery.0 said:
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
Click to expand...
Click to collapse
Wipe everything. Install your rom only. Does it boot?

exad said:
Wipe everything. Install your rom only. Does it boot?
Click to expand...
Click to collapse
no. It loads the splash screen for a second then goes to a black screen.

You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app

exad said:
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
redownloaded 3 times. erased cache. wiped everything and same problem as before loads splash screen then back screen

Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app

exad said:
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just making sure since I have only researched slightly, since im s-off If i run the latest unrootable RUU Id still be able to unlock bootloader and regain root?

What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium

Venomtester said:
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
every other rom ive flashed boots fine its only miui that gives me problems. It boots for other people fine so I dont think its the rom and I tried to install on CWM and still have issues

I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium

Venomtester said:
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
noob question but how do I find the md5?

avery.0 said:
noob question but how do I find the md5?
Click to expand...
Click to collapse
Search MD5 Sum Checker. It's a program that is pretty self explanatory and will check it for you. The MD5 is attached to the download. You copy it from the site and past it in the checker.

And after you s-off you don't need to re lock to ruu so you won't lose bootloader unlock
Sent from my HTC One X using xda app-developers app

Running the 3.18 RUU fixed my problems. Thank you both for the help
Sent from my HTC One X using xda premium

Cyanogenmod 10.1 installation

Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app

idomohr25 said:
Hi there,
I am currently installing Cyanogenmod 10.1 for my HTC Sensation. I'm stuck in the blue circle loading screen. (image below)
I don't know what should I do.
Help will be highly appriciated.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
probably you are on S-ON am i right?
if yes use 4ext recovery
enable smatflash from it
flash the rom
done
otherwise flash the boot.img of the rom via fastboot command

My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.

idomohr25 said:
My device is S-OFF.
I am trying to flash firmware again, and clear cache and dalvik.
Click to expand...
Click to collapse
Most of the time there is no need to re-flash firmware. Did you wipe data beforehand? maybe you can try another build (the from an earlier/later date). This might help.

Sometimes a complete wipe is needed...
Hi,
Sometimes when moving from one ROM to another a complete wipe and format of all partitions (except sdcard) is needed in order for it to work. Have you wiped and formatted all your partitions before flashing the ROM? I use Titanium pro to backup my apps before doing this.
You should be able to do this with any of the recovery programs. 4EXT is really good and easy to use for this. Also, if you don't already know this, you should flash the correct GAPPS for your ROM after you install the update. That way you will have everything you need on your first boot after your flash.
Good luck!

when i updated my firmware from 3.32 to 3.33 i got stuck at the same screen. Just booted to recovery and used 4EXT Recovery touch to wipe cache and dalvik, after that everything was fine

cant flash with cwm, stuck with aokp that dosent work.

I flashed aokp. I tryed to flash gapps but cwm says it cant read my sd and wont flash anything but su. My browser dosent open at all, my backups are gone. How should i go about flashing a rom that works?

What CWM are you on
Sent from my HTC One XL using Tapatalk

Did you perform a factory reset from the bootloader?
Sent from my Evita

Yes i did.
timmaaa said:
Did you perform a factory reset from the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
I did a factory reset, wiped everything, still nothing. Cwm keeps saying it cant open sd card when i try to flash another rom. I dont know how to fix my phone now. Would i be able to sideload it? And im not sure what cwm im on.

Ok but did you do a factory reset from recovery or from the bootloader?
Sent from my Evita