Database Develop

[Q] Sprint P100 can not wipe

Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?

just installed Astro, the program will crashed when launch it

Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?

Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.

Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.

Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....

There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.

you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)

I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk

Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance

as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share

Noob to the tab needing a little guidance *brick*

Ok, ill keep this quick and tidy. The tab was working just fine. I only used z4 root on it and it still was fine after that. The other day the battery died in it. I plugged it in to charge and now it only boot loops. I put it into recovery mode and i get this as an error.
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:can't mount CACHE:recovery/command
*MANUAL MODE*
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:can't open CACHE:log/recovery.log
E:Cant mount /dev/block/mmcblk0p1
(no such file or directory
I tried using the heimdall program to flash the ed02 files and it still gives this in recovery. Im at my wits end with this and really dont want to send it to sammy. Verizon will not honor the warranty due to the number being disconnected.
Can anyone help me with this so i dont have to send it in. Thanks

1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android/GT/Mirror/Recovery/CDMA/Verizon/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system)
put cache into cache
put param into param
put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache. reboot, and update to ec02.
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root. get that here: http://forum.xda-developers.com/showthread.php?t=803682
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!

boodafli said:
1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android/GT/Mirror/Recovery/CDMA/Verizon/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system)
put cache into cache
put param into param
put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache.
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root.
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!
Click to expand...
Click to collapse
nice guide though .... keep it up

can you tell me this guide for which tab i'm sure is not for the galaxy tab GSM
as i have sticky thread and i have empty place i'll like to add this guide sure after your proving
edit i got it , its for CDMA .. so can you accept that i post this guide under your name in my thread ?

it's for the verizon CDMA tab. and you can post it, it's supposed to be helpful. i lurked on these boards for like, 2 months before i got brave enough to try doing stuff to my tab. having a step by step process really made me feel like i was flashing with at least a little bit of a safety net.
k0sh said:
can you tell me this guide for which tab i'm sure is not for the galaxy tab GSM
as i have sticky thread and i have empty place i'll like to add this guide sure after your proving
Click to expand...
Click to collapse

oh hey. in your sticky, add this after 'now run superoneclick': get that here: http://forum.xda-developers.com/showthread.php?t=803682

boodafli said:
oh hey. in your sticky, add this after 'now run superoneclick': get that here: http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
will do sure , thanks

go check it here Post number 3
http://forum.xda-developers.com/showthread.php?p=14929111#post14929111

Ok i downloaded all the files and it is still looping on me. I went into the recovery and it is still giving me the same errors. Im at a loss here. I think it just may have to go to sammy. Im not that good with this. I really do appriciate all the help.

when you're in recovery, does it let you wipe cache and data? maybe try that, then reflash?

I tried with the updated version and e2 version of the software and anytime i go into the recovery its giving me that same line of errors. I think it might be a soft/hard brick. I may have to send it in to get serviced. Im just glad that if i do the stock software is flashed to it and they wont be able to tell the difference.
Edit:
Well after doing some digging it seems that the recovery partition cannot be loaded onto the disk. It looks like the internal sd card itself might be corrupt or fried. I have adb that i can try to do it with, but im just tempted to send it in. I am just hoping that they dont say that its no longer warranted.

Hi,
I was trying to upgrade to Gingerbread, and downloaded the FW files from samfirware.com. I used Odin to flash, everything turned out successful, except that my tab gets stuck at the Samsung logo screen. Any help would be appreciated?
Thanks

if you have a verizon tab, we don't have gingerbread yet. if you have a GSM tab, try booting into recovery, wiping cache, data, and dalvik, and rebooting. beyond that, since i don't have a GSM tab, i dunno what to tell you.
ashish.b said:
Hi,
I was trying to upgrade to Gingerbread, and downloaded the FW files from samfirware.com. I used Odin to flash, everything turned out successful, except that my tab gets stuck at the Samsung logo screen. Any help would be appreciated?
Thanks
Click to expand...
Click to collapse

Well samsung has fixed it for me. they had to replace the entire control board. I guess i really did a number on it. Whats cool is that its not going to be a verizon tab anymore. They have the hardware for it but the rom is stock like it was bought off the shelf. I cant believe it would fry like that after just charging.

[GUIDE] How To Receive OTAs Again If You Are On A Leak ***Proven Working Method***

If followed correctly, this a bulletproof method (reposted from our work at Rootzwiki) of returning any image to a true 5.5.886 stock and then applying the OTA update.
Commands/Screenshots
Moto-Fastboot Commands
Root Commands
Boot Mod Commands
***All the files you must have in one folder - Full Package from below***
Necessary Resources
Motorola Drivers v5.4.0 (32-bit) or Motorola Drivers v5.4.0 (64-bit)
5.5.886 Radios (radio.zip)
Full Package of All Other Files You Will Need: Link 1 or Link 2
Optional Resources
5.5.886 Boot Mod
5.5.886 FXZ Restore File
Motorola Fastboot
Root and Forever Root Files
ADB-Fastboot Files
5.5.893 OTA Update
RSDLite v5.6
Fastboot Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down twice, till "AP Fastboot" is selected
Press Volume Up to select
Recovery Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down once, till "Recovery" is selected
Press Volume Up to select
When the icon with the android and exclamation appear press both Volume Up and Volume Down at the same time to enter the recovery
Step-by-step Process
Download the 3 files under "Necessary Resources"
Install the appropriate Motorola drivers for your operating system
Place the radio.zip file on the root of your SD card (not internal storage)
Unpack the full package of files to one folder on your computer
Turn off your phone completely
Start into Fastboot Mode (listed above)
Connect your phone to your PC with the USB cable and let it install the drivers for your device
After the drivers are done installing, open a command prompt in the folder where you unzipped the full package to
Using the Moto-Fastboot Commands screenshot from above follow each one step by step until you are done
When you have finished, disconnect your USB cable and press the Power button once to turn it off
Start into Recovery Mode (listed above)
Highlight "wipe cache partition" and press the Power button to select it
When it has completed, pull the battery out of your phone and then put it back in
Start into Recovery Mode again
Highlight "apply update from sdcard" and press the Power button to select it
Highlight the "radio.zip" file on your SD card and press the Power button to select it
When it has completed, highlight "reboot system now" and press the Power button to select it
When the device reboots into the OS waited 1 minute for it to load everything in the background
Follow the prompt but don't sign into anything, just get to the homescreen
When at the homescreen, connect your USB cable and then from the pull down menu select "USB connection", then select "Charge Only" and hit OK
Go into Settings -> Applications and enable Unknown Sources and hit OK
Go into Development and enable USB Debugging and hit OK
Back out to Settings -> Battery & data manager -> Battery mode and select Performance mode
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Root Commands screenshot from above follow each one step by step until you are done
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Boot Mod Commands screenshot from above follow each one step by step until you are done
***When a Superuser prompt appears on your phone after the last command, quickly select Allow and make sure you do NOT reboot your phone***
When it has finished, connect your phone to your 3G/4G or a WiFi connection
Go into Settings -> About phone and select System updates
When the prompt comes up, press Setup
Place a check in "I agree to the Motorola Terms of Service" and then press Next
When the update prompt comes up, press Download
Wait for the update to download
When the update prompt comes up, press Install Now
Let update reboot to recovery and install itself
***Your phone may appear as if it is completely off for a little while but leave it be it will turn itself on and continue***
Let the update finish and then it will reboot back into your system
Congratulations! You now have the official 5.5.893 update installed and are back on the official OTA path and forever rooted
Credit to all developers of the zergRush exploit, to realbbb (from Rootswiki) for discovering the Boot Mod, and anyone else who participated in making this all possible.

I have edited the instructions to make things easier. I have included the entire package of all the files you will need under "Necessary Resources".

The official fully detailed guide is now up. Please feel free to comment if you have any questions, concerns, or need help.

The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!

Hey guys I got a little problem, unfortunatly you guys have generated so much traffic on my Dropbox account that they suspended it for 3 days. I'm going to ask if any of you guys have the full package file to please upload somewhere for a few days and post a link here until my account has been unfrozen. In the mean time you guys can use the optional files to recreate that package listed in the 4th screenshot. I greatly apologize for this inconvinience.

cellzealot said:
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.

GertBFrobe said:
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.
Click to expand...
Click to collapse
dd=raw image
i think or at least it does to me being in computer forensics
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
someone please share a working link for those files.

As soon as your account becomes unfrozen I'll download the "full files package" and try to upload to Megaupload or something like it to have them permanently downloadable.
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Also, I too would like to keep my data and would like to do the simpler way. please clarify what DD means in the above post?

Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.

So I think that I will do this. Lets says I get to 5.893, install safestrap, and on my non safe 'strap' ie, my daily driver, I restore a nandroid backup of the ROM I am running now (eclipsev 2.0, 5.7.893), Will this work? And theoretically I will have the same system I do now, but with 5.5.893/new radio/kernal/on the update path... That all sound about right and doable?
Sent from my DROID BIONIC using xda premium

You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.

cellzealot,
Thank you for all the time you have contributed to participating in the work of this method. I appreciate your continued effort in order to slim down and automate the steps I have listed. I do encourage anyone interested to feel free to use this method instead of mine. However for those who are more interested to take the manual route and prefer to be in full control of what's going on with your device (maybe learn a few things along the way too), I will be keeping this method up and hopefully my Dropbox account will be unfrozen in a few days so the full package can be downloaded again. In the mean while, if anyone still has this file please PM me a link when you can upload it elsewhere and I will have it updated.
Thanks again,
Open1Your1Eyes0
EDIT: FYI, for all those you who want to keep their data just skip the last command in the Moto-Fastboot commands screenshot. The command is "moto-fastboot -w". Skipping this will leave your data intact. However, note that because everyone's data is different, I cannot guarantee this will work for everyone so please note that it is no longer considered "bulletproof" in this case although most likely should work.

cellzealot said:
You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.
Click to expand...
Click to collapse
So are you saying you can't do this to get back on the path and then install safestrap? Maybe i am not understanding something somewhere but i would think you could do this then use safestrap to install a custom rom then when a new update comes from verizon just switch back over to update then if you want go back to your safestrap just go back over. can someone explain this?

Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium

ticrandall said:
Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Wonderfully explained! Thank you

cellzealot said:
Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.
Click to expand...
Click to collapse
And this is exactly as it should be.
I was one of the first to try the method out, and my set of steps was a lot simpler, as I had not hacked my webtop, and neither had I removed any apps from the system area either. All I did the was revert to stock rooted 43v3r r00ted system with r3l34s3d r00t, revert radio, dd kernel, then flash ota.
Now that you guys have stepped in and cut the fat out, I think a lot of people are going to be much happier with the whole process, happier and more comfortable, which is a major factor with this sort of thing.
Thanks again, cz, p3 and anyone else refining the process, and especially thanks to 0 open for detailing the steps in the beginning, and a huge thanks to real BBB for providing me with the files to dd the kernel when I started doing all this.
This is why I love my bionic and Android in general - you guys rock!
Sent from my DROID BIONIC using Tapatalk

This makes me happy to see this. I was worried about getting back on the upgrade path. Thank you to all those involved in this!

Hey guys,
So I'm finally home and now had a chance to access my files. I'm choosing to forget about Dropbox because I cannot wait for them any longer since I've been getting a lot of PM's requesting this file. I have edited the OP and all file links are updated and working. The full package has been moved to MegaUpload instead. Anyone who was waiting before the method is now fully working and ready for use. As always please feel free to comment if you need any help or have any questions. Thank you for your patience and once again I apologize for the delay.
Thank you,
Open1Your1Eyes0

If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.

TheMuffStuff said:
If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.
Click to expand...
Click to collapse
Where can this be found? I haven't been able to locate a link for it.
Edit: Appears to be here: http://www.droidforums.net/forum/dr...ates-your-modified-motorola-droid-bionic.html

Boot loop problem

Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.

A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.

boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!

This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.

Thanks! I'll give this a try when I get home. I'll let you know how it works out.

Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .

spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium

I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.

spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.

spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.

prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD

It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!

mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.

[Q] CWM gives me a status 7 error when installing cm91

I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated

gardarh said:
I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated
Click to expand...
Click to collapse
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean

erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Thanks for the reply!
Regarding JB, I'd rather want a stable cm build as this is my dad's phone and I'd rather not set him up with something branded as experimental (yes, I bricked my dad's phone ). Regarding GB, I'll give it a try but I'm wondering if the cm installation for GB doesn't have the same assert checks as the installation for ICS...rendering me in the same mess (I don't have the device with me right now but I'll try later today).
Is there a way to get the Samsung stock ROM somewhere?
- That way I'd at least have known a way out of this mess.
Also, I'd like to know WHY this is happening, as I'm curious about where these values are stored and how one changes them.

erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Tried cm10, same error (as I expected). I edited the install script, removing the assert line. This only makes the device go unresponsive on install. I can't mount the system partition (or any other partitions for that matter)... the device appears fubar. Gonna try to use odin to install some stock rom I found. Not very optimistic though.
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?

gardarh said:
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?
Click to expand...
Click to collapse
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

xsenman said:
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hey xsenman,
I think I actually already stumbled upon your posts, I believe I did a PIT restore with the 512 pit and Odin just hung (for an hour or so) before I unplugged. This aggravated my situation (I realized through this whole process that there are multiple levels of fu*ked when rooting).
I finally found a way out of this mess just an hour ago by following this post: http://forum.xda-developers.com/showthread.php?t=1102881 . I reinstalled the stock ROM and then installed cm91 again and now the device is working fine. Odin did hang on me once again when I followed those instructions but I tried again, using the 803 pit file and then it finally worked (don't know if it was a coincidence).
So the state I was describing before was that the partition table was corrupted. From there nothing works (obviously).
Thanks for taking the time to help me out! I have to say I wasn't very optimistic there for a while...
Cheers,
Gardar

Noob with a similar problem
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules

JulesBell said:
Any help is greatly appreciated.
Click to expand...
Click to collapse
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals

Sounds like you're not more of a noob than I am
From what I learned from my battle the assert(...) failures indicate that that the device type cannot be read anymore which in turn indicates that the filesystem storing that information is corrupted (and/or the partition table defining your filesystem). Btw. if you extract the .zip file containing the cm mod and do a "grep -r assert" you can find the installation script (don't remember exactly where it's located right now). It's not very helpful but informative...
The filesystem mess can be fixed with flashing a new pit file (I recommend this post on pit files which seems to be a phenomena specific to Samsung phones), then installing one of the stock ROMs in the post I linked and finally reinstalling CM (which I believe repartitions your internal sdcard again). I think you want to do both the PIT and the stock ROM in the same go with Odin. Of course this is pretty much the same as I said in the post above and therefore probably isn't helpful to you, but it worked for me
Good luck!
JulesBell said:
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules
Click to expand...
Click to collapse

-
xsenman said:
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals
Click to expand...
Click to collapse
Hey again, xsenman and gardarh,
thanks a lot for the quick replies.
I want to go and try to follow the directions you guys gave me, but first of all some additional info and corrections that I forgot or stated wrong after a long night of browsing this and other forums and desperately trying to get my phone working again.
- regarding the model and original firmware: I'm pretty sure it's just the plain sgs gt-i9000 (without the "M"). The latter version seems to be specific for the Canadian/North American market, and my phone (like me ) is from Germany. Also, in the phone status info menu it just said "i9000" when the phone was still working. And I may have been mistaken about the version number 2.3.3, it might as well have been 2.3.6.
I only recently (this week) bought this phone used from a friend. I'm not sure which firmware version the phone was originally shipped with, but since my friend is not a tech geek, I think it is safe to assume she only installed SAMSUNG-official updates.
- then, I think THIS IS IMPORTANT, I think the EFS files may have been corrupted and the IMEI may have been lost when flashing the radio module and the GPS fix, which I guess may have caused the phone to lose network service and not be able to scan for networks.
Will this be miraculously restored when flashing to stock 2.3.6 from an original ROM or do I need to extract the IMEI some way BEFORE I go ahead and re-partition the internal SD card?
- do I need to re-partition anyways? I tried to mount "/system" in CWM and it failed.
- also, I forgot to mention that after the failes recovery from my backup, I couldn't even get to CWM Recovery anymore. I flashed the hardcore kernel onto the phone again via USB using Heimdall, so now I can access CWMR again.
Thanks a lot!
Cheers
Jules
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
I just discovered that there seems to be a backup of my EFS folder after all, which was created at the same time as the nandroid backup. I copied the backed-up "efs" folder to the root directory as well as my PC just to be sure. Copying the folder to root doesn't seem to have any effect on the bootability of my phone though.
However, finding this backup gives me some confidence regarding acomplete reset to stock with an original ROM and PIT-file, so I'll go for that now and update you on the results.
Cheers,
Jules

phone restored
Thanks a lot guys, with your help I was able to restore my phone to a stock GB 2.3.6, using
i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq
Right now I m just happy it's working again and not in the mood to flash to cm9.1 again, fearing i might hit the problems with GPS and fm radio not functioning again... any suggestions?
Best wishes
Jules

In my limited experience, if you cannot mount /system your filesystem is probably corrupted (at least that was the conclusion I came to).
You should not be worried about which android version the device was running (e.g. 2.3.3) but you do have to be careful about choosing which region the firmware was designed for. See if you can find your device type here:
http://www.sammobile.com/firmware/?page=3
Take note of the code under the PDA column.
The download from that site didn't help me though, but should hopefully help you in finding the correct stock firmware (from my link above).
Chainfire posted some info about stock rom names (See http://forum.xda-developers.com/showthread.php?t=1103399 undir the section "Help! Which file do I use ?". It's for Galaxy S2 but I believe the idea behing the naming is mostly the same.

problem solved
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know

salival eedfie
JulesBell said:
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know
Click to expand...
Click to collapse
Good to hear! Which rescue kit (for future reference)?

abc
gardarh said:
Good to hear! Which rescue kit (for future reference)?
Click to expand...
Click to collapse
>>> i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq <<<
from xsenman's list.
Cheers,
Jules