Database Info

[FIX] Status 7 in Clockwork Recovery on Nexus S 4G during zip flash

I kept getting flash issues after using the unlockr's root method on my Nexus S 4G, specifically the inability to flash roms due to a status 7 error.
BEFORE you run around searching every forum, or use someone else's old nandroid to revert to 2.3.1, or do any craziness... if you flashed Clockwork via fastboot, install ROM Manager from the market, and install the latest ClockworkMod recovery via Rom Manager, and give it another try.
Hopefully this is easy enough to find, that no one else has this problem.
Happy hunting

Hi,
This didn't help
I installed ROM Manage from Play Store and tried to install ClockworkMod recovery from ROM Manager. Howeve, it kept on getting stuck while installing ClockworkMod recovery....
Are there any other solutions for Status 7 error?

Flash the latest CWM manually via fastboot. Have a look at the Nexus S rooting guides, they all detail how to flash a custom recovery.

Yep, it was all about updating the CWM. In my case I had to update it to the one that supports touch mode (don't remember the version number). Once that was done all went quite smoothly.
Sent from my Galaxy Nexus using XDA

Brother may have messed up my phone!

Hey everyone,
My little brother is trying to learn more things about mobile devices and wanted to have a go at my old piece of junk, stock optimus one p500h. So i let him have a go and now it's not working so here is the problem.
First he rooted it and that worked fine with gingeroot and then proceeded to install romanager which bricked the phone but he was able to recover the phone with a recovery.img and using LGMDP-v1.5 and emergency mode.
After that he installed some android system recovery thing "RA-thunderg-1.2.0-gnn" not sure what the software was originally, regardless he tried flashing from the flash from zip from sdcard and used a cyanogenmod zip which he said worked and then the phone said success and rebooted.
Now the phone just sits at the cyanogenmod loading screen and will not boot.
I am able to get into the recovery menu with home,down and power and emergency mode also works.
Where did he go wrong and what does he need to do in order to get this to work properly? Thanks for your help everyone and sorry if the post is a bit disjointed i'm trying to translate what he's saying into the post xD

forthecake said:
Hey everyone,
My little brother is trying to learn more things about mobile devices and wanted to have a go at my old piece of junk, stock optimus one p500h. So i let him have a go and now it's not working so here is the problem.
First he rooted it and that worked fine with gingeroot and then proceeded to install romanager which bricked the phone but he was able to recover the phone with a recovery.img and using LGMDP-v1.5 and emergency mode.
After that he installed some android system recovery thing "RA-thunderg-1.2.0-gnn" not sure what the software was originally, regardless he tried flashing from the flash from zip from sdcard and used a cyanogenmod zip which he said worked and then the phone said success and rebooted.
Now the phone just sits at the cyanogenmod loading screen and will not boot.
I am able to get into the recovery menu with home,down and power and emergency mode also works.
Where did he go wrong and what does he need to do in order to get this to work properly? Thanks for your help everyone and sorry if the post is a bit disjointed i'm trying to translate what he's saying into the post xD
Click to expand...
Click to collapse
If running a Windows PC and the device can boot in to fastboot, you can use Android Flash Recovery ( link in my signature ) to flash another recovery image. There are some more complicated ways using ADB, but well try to avoid them ATM You can also use LGMDP to flash a different recovery image. There are several floating around here at XDA.
As for where he went wrong, I cannot say. Piece of advice, if in doubt - don't do it.
Have you tried booting to recovery and wiping cache and dalvik cache then attempt to boot to Andorid?

shinobisoft said:
If running a Windows PC and the device can boot in to fastboot, you can use Android Flash Recovery ( link in my signature ) to flash another recovery image. There are some more complicated ways using ADB, but well try to avoid them ATM You can also use LGMDP to flash a different recovery image. There are several floating around here at XDA.
As for where he went wrong, I cannot say. Piece of advice, if in doubt - don't do it.
Have you tried booting to recovery and wiping cache and dalvik cache then attempt to boot to Andorid?
Click to expand...
Click to collapse
thanks for the fast reply, looks like recovery is gone now? I had attempted to clear the cache though. Would you mind giving me a step by step as im unsure of what i need to do now xD not sure what i need downloaded or to do what with what after my brothers done all this haha

Just flash a recovery from LGMDP for your phone.. then download a rom for your phone and wipe everything in recovery and flash the rom
And do not flash stock rom from kdz or lgmdp if you cannot boot your phone. It has high chances of bricking

Junior Einstein said:
Just flash a recovery from LGMDP for your phone.. then download a rom for your phone and wipe everything in recovery and flash the rom
And do not flash stock rom from kdz or lgmdp if you cannot boot your phone. It has high chances of bricking
Click to expand...
Click to collapse
ok now it's running again and sadly it's giving me an unkown baseband and no service now! I tried flashing to the old legacy baseband for cyanogenmod 7.2 / 2.3.7

forthecake said:
ok now it's running again and sadly it's giving me an unkown baseband and no service now! I tried flashing to the old legacy baseband for cyanogenmod 7.2 / 2.3.7
Click to expand...
Click to collapse
Cm7(except a very old one from mik_os), stock gb and up requires new baseband. You can search for baseband fix and install through recovery ( I don't remember if it's old bb fix or new bb fix, try for yourself )
You can also search how to install new bb permanently but it's more difficult and has(I think) chances of bricking your phone
Sent from my LG-P500 using xda premium

Phone in bootloop

Hello,
I rooted my phone the day I got it and flashed TWRP on it
I installed the 3 OTA updates and thus lost root+(unfortunately) my recovery.
Therefor today I tried installing my recovery again.
(talking about this one: http://forum.xda-developers.com/showthread.php?t=2766186)
After I installed it I got into a bootloop, I've tried the newer version too now.
After that I tried putting the new franco kernel on it(r14)... No succes.
Can anyone recommend what to do now?
(I can not enter recovery..)
Please help me

I was thinking, if the new OTA update appears on cyanogenmods site.
If I download it and then only flash the kernel and recovery with fastboot, will that work?
I really don't want to lose all my data!

Did you untick Update CM Recovery in developer settings after installing TWRP?
Sent from my LG-F400S using XDA Free mobile app

ROM Flash Gone Wrong

Okay, so I'm pretty conflicted/concerned. So I guess I should explain how I ****ed this up. Well, I was pretty tempted to flash PA Beta 4.6, it really looked good to me. But having not flashed on my Nexus 5, I didn't have a custom recovery, so I installed flashify and TWRP and set it up. Went well. Then I downloaded PA Beta 4.6 and also flashed it, took a bit, but I got it to work. All is good right? Well, I was confused at the lack of Google Apps (Play Store, Youtube, G+, you know). So I went into the recovery and wiped my data and tried to flash again. Only problem is, I accidently also erased the download for PA Beta 4.6. So, I get home (I was doing this all at school) and try to flash the factory images for 4.4.4 Hammerhead. But I cant seem to get it to work. When ever I use fastboot and flash the images, I end up with either 1. Non stop Google screen when I boot up, or 2. A picture of an Android with his front hatch opened and a red triangle with an exclaimation mark. What do I need to do? Please help!!

The android on his back is the stock recovery. Just hit vol up and do a factory reset. That'll fix your problem of booting
Sent from my Nexus 5 using XDA Free mobile app

You have to flash google apps aka gapps separately after flashing the ROM

ldubs said:
You have to flash google apps aka gapps separately after flashing the ROM
Click to expand...
Click to collapse
This. And don't flash custom firmware without PC access.

if TWRP is still working I would use ADB or FASTBOOT to push the PA Beta 4.6 ROM or another rom to your phone and then use TWRP to install it... sounds like you just wiped your SD card so move the ROM you want back to the phone and try try again.... GOOD luck hope everything turns out!

[Q] Upgrading after factory reset

Ran into a problem yesterday (I'm not sure exactly what), but my phone was hanging on the HTC One loading screen. I used my TWRP 2.4 to factory reset. I am unlocked and can get into bootloader fine but cannot flash anything (I am using the HTC One S All-in-one kit by Hasoon2000). The reason I am trying to do this is I want to reinstall to the latest OTA update which I believe was 4.1. (3.14.531.17), but when I try to update it takes me first to the TWRP, and when I try to install it from there it fails.
Help would be greatly appreciated, and seeing as this is my first post, I apologize in advance if I'm posting in the wrong place or something.

I'd start installing the latest TWRP version, which should be the 2.8.x.x. Other than that, I don't know...

Fiabeschi said:
I'd start installing the latest TWRP version, which should be the 2.8.x.x. Other than that, I don't know...
Click to expand...
Click to collapse
I was able to get 2.8.1.0 installed through TWRP Manager from the play store, still can't upgrade the stock rom though.

For reference, I was able to get the stock recovery installed using Flashify from the Play Store. The OTA went smoothly after that.