Database Develop

I screwed something up.

I was rooted and running CM6. I tried getting back to a stock 2.2 by flashing the stock image from Rom Manager. I downloaded the 2.2 update from google and it wouldn't update. In the system menu or bootloader I got a little format happy with boot/system and so on. Anyway, doing a nandroid now. Is there anyway to get this phone back to the kernel it shipped with?

You have to flash it with the stock recovery.

I've been using that Universal androot.http://www.androidappjudge.com/2010/08/one-click-root-application-universal_10.html I tried flashing stock 2.2 and I didn't read the two options, I just clicked them and kept going not realizing that I flashed the rooted, superuser version. Does this mean that I'm now rooted forever? When I try flashing stock 2.2 with rom manager It stops @ the android and /!\ symbol. Now it's even doing this with CM.
I'm now wondering how to get rid of whatever crap might be floating around on my phone and why it may not be flashing anymore?

there is nothing wrong, rooting allows you the ability to have super administrative rights. Since all you have done is grant yourself admin rights, the recovery should be the same.

Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.

glwinkler said:
Something is wrong. I can't Fix Permissions or flash anything.
Man, I should have just left it alone.
Click to expand...
Click to collapse
Did you wipe? I used 1-click root and I hadn't flashed anything in over a year so I forgot to wipe and I boot looped until I pulled the battery, booted into recovery and wiped. Simple solution but it could be worth mentioning...

So you are saying that, you have the stock recovery now? Triangle with little android? If so, Just download a PASSIMG.zip and flash through bootloader. This will take you to stock.
I have an N1 with locked bootloader and when I wanted to go back to stock(Forgot to get a nandroid of unroot rom). I had to flash a stock recovery. then downloaded the PASSIMG.zip from here http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91+downgrade
This takes me back to ERE76. Then I download an OTA of FRF85B.

I think fix permissions fixed everything. Thanks for the tips!
THIS HELPED TOO:
http://forum.xda-developers.com/showthread.php?t=619153

[Q] Noob here

So my friend wanted to root his captivate and wanted to flash the spaceman ROM so heres what hes done so far
1.He used Z4root and perma rooted his phone.
2. Downloaded ROM manager and flashed clock work recovery
3. He did a backup and downloaded the ROM
4. He went into recovery and cleared cache factory and data.
5. Tryed to flash the ROM
6. It didnt work....
7. Restored the Backup
8. His phone wont download anything
9. He unroots with Z4root
10. Still nothing phone wont download stuff from market so he re roots with Z4
11. I Write up this thread
SO heres the ?s
What went wrong ?
Did we miss something?
If possible can we get a link to step by step instructions on how to root and flash ROMs

This does not belong in Development.

Moved to Q&A.

IIDIncII said:
So my friend wanted to root his captivate and wanted to flash the spaceman ROM so heres what hes done so far
1.He used Z4root and perma rooted his phone.
2. Downloaded ROM manager and flashed clock work recovery
3. He did a backup and downloaded the ROM
4. He went into recovery and cleared cache factory and data.
5. Tryed to flash the ROM
6. It didnt work....
7. Restored the Backup
8. His phone wont download anything
9. He unroots with Z4root
10. Still nothing phone wont download stuff from market so he re roots with Z4
11. I Write up this thread
SO heres the ?s
What went wrong ?
Did we miss something?
If possible can we get a link to step by step instructions on how to root and flash ROMs
Click to expand...
Click to collapse
After rooting, did the SuperUser App appear in the app drawer?, if so, the phone was rooted and the steps you took appear fine to flash the ROM. Don't know what you mean by it didn't work (error msgs or what?) Also, don't know what or how you're trying to download something. Perhaps if you can provide more information, we can help

I'd suggest reading this post here.
Also I would have him Odin 1-click back to stock and start over.
Plus in the future please post what the error was as it would help determine your next troubleshooting steps better.

Yes superuser did appear in the app drawer.
When we tryed to flash it said operation aborted i dont know why.
And he is trying to download apps. from the market and its not working lol

Yup.. I'd flash back to stock then re-root. Sounds like something went screwy when you attempted to flash the ROM.

We restored the back up before attempting to flash the rom so would that be okay instead of flashing back to stock?
Also is there a way to back up all the apps so if do flash back to stock we can get them back instead of re downloading everything again?

IIDIncII said:
We restored the back up before attempting to flash the rom so would that be okay instead of flashing back to stock?
Also is there a way to back up all the apps so if do flash back to stock we can get them back instead of re downloading everything again?
Click to expand...
Click to collapse
Download Titanium Back-up from the market (if you can)

[Q] stuck in broken recovery mode

Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz

No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.

cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz

Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.

I9305t 4.3 wont boot

HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.

flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...

spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.

try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...

spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat

Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.

Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!

Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers

Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.

Tried Flashing Kitkat - Soft bricked?

Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?

If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005

andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?

Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.

andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?

Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?

Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?

Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.

steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!