Hi all,
I recently decided to upgrade my 1 year old Samsung GT-P1000 tablet from its stock Froyo to a newer Gingerbread-based ROM. The tablet is not SIM-locked.
I tried using Heimdall to flash Technomancer's CM7 beta but I ended un in the CWM 5.0.27 recovery screen every time. I tried rebooting a couple of times, repartitioning and not, formatting EVERYTHING (/system, /data, both SD cards, etc) and I always end up in the recovery screen.
I also tried installing MIUI from the available CWM and again I ended up in the recovery screen. The only visible effect was that it downgraded my CWM version to 4.x (which I can upgrade with Heimdall flashing CM7 again).
While in the recovery screen I can connect from my computer using ADB and get a root shell (at least whoami replies with root).
I'm probably missing something really basic but I've been looking at many other posts and haven't been able to figure out what. Is there any extra step that I need to take in order to get a bootable system?
Thank you!
Wipe data in recovery
Sent from my SCH-I800 using XDA App
Already did that :-( I tried wiping data, cache, and still it goes back to recovery after rebooting.
Try flashing again with a different rom and telk me what happens
Sent from my SCH-I800 using XDA App
Press two times on the home button if you are in recovery
Sent from my GT-P1000 using XDA App
Frank2623: I tried doing that and the home button only moves the cursor. I tried other buttons as well but to the same effect, they only act as cursors and OK/back, no other effect observed.
YoshiFan501: After flashing CM7 for GT-P1000 I did try with MIUI 1.11.4 (Final Update), only I didn't know how to flash it from Heimdall and I just ran the update from recovery. I am also trying to locate other ROMs for Galaxy Tab. Any suggestion?
I did the exact same thing this guy did and have the same problem. Stuck in a recovery boot loop.
Did the same things, wiped everything, flashed different roms, miui etc, can't get out.
Can anyone provide a solution to this or tell me how to flash back to my old T-Mobile stock rom? I didn't brick my device did I?
Solution
Ok so I managed to get at least a stock 2.3 ROM, which is better than 2.2 and much better than not booting!
Here's what I did, in case someone else like Lucifus comes here with the same problem:
* Google for a stock GT-P1000 ROM like 001001-GB-Stock-Safe-v5.zip. Unzip it in a directory and untar the bundled GB_Stock_Safe_v5.tar as well.
* Install Heimdall v1.1, NOT v1.3 and open Heimdall Frontend (on 1.3 it wouldn't let me perform the following steps, maybe you get luckier)
* Turn on the tablet in download mode (with VolDown + Power)
* In Heimdall, select the PIT file from the 001001-GB-Stock-Safe-v5 and also the rest of components: primary boot (boot.bin), secondary (sbl.bin), factory FS, ...
* Choose a modem file (the Start button will remain disabled until you do). A quick google showed JPZ being the correct one for Android 2.3 and I for me it actually works.
* Recovery can be left blank
* Flash the whole thing
* It will reboot in recovery and output text on screen, including some errors
* Select factory reset, otherwise when you reboot again it will be stuck in the blinking Samsung logo (but you can power off, reboot in recovery and select factory reset then).
* Finally the Android OS boots
Not Detecting in ODIN/ How to use Heimdall
Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i swith the damn thing off completely
I have tried to go in download mode. odin doesnt reognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS i im not worried about my data , and i have not backed up the rom etc before doing any of these)
blizzard_boy said:
Hello xda users,
I need HELP !
I have a galaxy tab P1000
currently froyo 2.2
wanted to upgrade to GB
Tried the Odin way from another link on this site (MANUAL updation for galaxy tab(p1000) into 2.3.3 gingerbread ), it failed and the Tab got soft bricked,
somehow managed to unbrick it, now its back to its original fw, but it keeps restarting in a loop until i swith the damn thing off completely
I have tried to go in download mode. odin doesnt reognise it , tried differnt computers too, no use.
I have gone in recovery mode, hard reset, wipe cache , still when i switch it on, it goes in a reboot loop.
tried to use heimdall. cant get sucess as i might not understand how to use it properly
Please help.
Sincere thanks to you if you can help me get my tab up and running., if not in GB atleast back in froyo.
(PS i im not worried about my data , and i have not backed up the rom etc before doing any of these)
Click to expand...
Click to collapse
Hmmm... did you READ the post just above yours ?
yes
i read , nothing helped
anyway i managed to get it detected in odin and flashed it through a proper walkthru process from another site.
now my tab works with GB
Libon
Related
Hi all,
For the last couple of days I've been trying to flash my Galaxy S with ICS333 using the following guide - http://forum.xda-developers.com/showthread.php?p=25722239#post25722239
-----------
"3. Enter Download Mode, open Odin, check Re-Partition, press PIT button and browse for the PIT file, press PDA button and browse for the PDA file in the ROM folder, press PHONE button and browse for the PHONE file, press CSC button and browse for the CSC file and finally press START button.Wait till it`s finished and when the phone reboots disconnect from PC.
4. When the phone has booted into the ROM and you see the wizard screen just enter download mode again, plug your phone into the PC, open Odin, press PDA button and browse for the CF-Root kernel, press START button and wait for it to finish.After the phone reboots disconnect it from the PC, let it boot and when you`re in the ROM, set your phone to mass storage mode from settings>wireless & network>usb settings and plug your phone into the PC, copy the ICS333 ROM to your internal SD root location, assuming you have downloaded it from here : http://goo.gl/LuXvH and disconnect from PC.
5. Enter CWM, Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache and flash the ROM.You will notice the phone will reboot immediately because it will switch kernels, from CF-Root to Semaphore, prior to flashing the actual ROM.As a result, it will boot loop or get stuck on Semaphore logo, so just force it into CWM using the 3 key combo (no need to take the battery out).Now flash the rom again and wait till it`s finished and > Reboot to system!."
-----------
After performing stage 3 I waited for the phone to restart and understand that I should have seen a ROM/Wizard appear. This did not happen and now the phone just goes straight into CWM upon boot.
Whilst in CWM I get the error E:Can't mount /sdcard/ and non of the functions work. What should I do next? I've had a search around these and other forums but can't work out what to do. Don't want to just keep trying random things and end up making the situation worse.
Thanks for any help you can offer.
Louis
king llama said:
Don't want to just keep trying random things and end up making the situation worse.
Click to expand...
Click to collapse
get back into download mode to flash a rescue kit or a JVU upgrade from My Android Collections also tick update bootloader
But First power down, pull out Battery, SIM CARD, and EXT SD card, press power button for a minute , than power up without SIM and Ext SD Card...make sure you have more than 50% battery charge before you attempt any sort of flashing
Thanks very much for the help. Used the darkyrom resurrection kit and it worked like a charm.
king llama said:
Thanks very much for the help. Used the darkyrom resurrection kit and it worked like a charm.
Click to expand...
Click to collapse
One last thing before I go ahead and try flashing ICS again. Can I go straight from darkyrom to ICS or do I need to put a Gingerbread installation on the device first?
Thanks again
Louis
king llama said:
I need to put a Gingerbread installation on the device first?
Click to expand...
Click to collapse
nope, should work from there
xsenman said:
nope, should work from there
Click to expand...
Click to collapse
Sorry to be a bother again but I now have a new problem. I have updated to CM 9 android version 4.0.4 which appears to function correctly but gives me no access to the sim card (can't see any phone numbers/contacts and won't connect to the network).
I understand that this usually has something to do with EFS settings (I took a backup of the EFS using GPS Aids before I flashed) which I have tried to restore using Nitrality but with no success.
I have checked the sim card in another phone and it works correctly.
Starting to think that this flashing business is not for me.
Any ideas as to what I should try next?
Thanks
Louis
You can change the efs folder via terminal but I found the easiest way (I had incorrect imei on hellybean) was..
Flash stock GB via Odin. Flash semaphore kernal via Odin. To get cwm.
Boot into recovery and flash cm7, boot into recovery and flash cm9, boot into recovery and flash cm10.
Obviously make sure you have cm versions on the card first. Efs corrupts when you don't flash in order example GB to JB missing out ICS. Doesn't happen all the time but that's usually the cause.
Worked like a charm for me.
sent using my fat fingers from the robot eating the apple...
creative0100 said:
You can change the efs folder via terminal but I found the easiest way (I had incorrect imei on hellybean) was..
Flash stock GB via Odin. Flash semaphore kernal via Odin. To get cwm.
Boot into recovery and flash cm7, boot into recovery and flash cm9, boot into recovery and flash cm10.
Obviously make sure you have cm versions on the card first. Efs corrupts when you don't flash in order example GB to JB missing out ICS. Doesn't happen all the time but that's usually the cause.
Worked like a charm for me.
sent using my fat fingers from the robot eating the apple...
Click to expand...
Click to collapse
I have returned the phone to stock Gingerbread and the problem still persists.
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
if you can get back into recovery, you should be able to press "restore" assuming you backed up your previous ROM.
cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Dude, you sir, are a life saver. I couldn't find the info that the link you just posted anywhere. Now I can fix my phone, lol..
Sent from my PG86100 using Tapatalk 2
Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
xxxx
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Sorry xda wouldn't let me post, reCaptcha wasn't working for some reason. Realized your link wasn't allowing me to reply lol
Anyways, Thanks a lot, that got me back up to stock and working, and I was able to reflash a custom rom (flashed to Rom slot 1, then backed up, and recovered into the stock slot). :good:
Now, I dont usually open threads, but I have an issue here. I've searched and read a lot on how to recover the U8800 in case its soft-bricked, but I've tried the reflashing 2.2 method (Fails in about 5 seconds), Linux method (blefish's method, buzzcomp's method could not yield any results. I connected the phone in the bootloader mode (pink screen) to a Linux PC, but it doesnt appear as a new device there.
Then I tried to upgrade to 2.3, it installs fine, automatically enters recovery (formats data, cache etc), reboots a lot of times (bootloop?). So now whenever I on my phone, the Huawei logo just keeps flashing.
I've also tried to replace the files when connected in the pink screen by replacing the boot.img , recovery.img, amss.bin , EMMCBOOT.mbn file, yet it bootloops.
Prior to this, I had downgraded from Aurora to the stock 2.2, which worked fine. Then I replaced the stock recovery with CWM (the correct one, not the U8800 Pro's). I did the usual clearing of cache, data, formatted system, wiped dalvik cache in order for me to upgrade to a new ROM. Everything went downhill from there
UPDATE : I managed to get 2.3 to be installed. But everytime I enable "USB Debugging", upon the next reboot, there will be a lot of apps which closes unexpectedly, like the Huawei Launcher, Google Framework etc etc. I've tried B526 and B528, but everytime I have "USB Debugging" enabled, this happens. It works fine on 2.2 though
UPDATE 2 : After my fresh installation of the official 2.3, I'd changed the launcher to Holo Launcher, but it fails at starting up. If it does, it keep saying that Holo launcher has closed unexpectedly. The only way to fix it is to boot into recovery and wipe data.
Any help?
bump
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
yusopa said:
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Where can i find the stock partition flash file?
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
Click to expand...
Click to collapse
hey i have this same mistake, i have the first boot fine after installing the official rom, but when i reboot the phone in normal boot (diisable fastboot) the phone gets bootloop, so i can't root it in order to put a new rom. i've downgrade to 2.2 froyo and get sum errors after installation but seems to work fine with 2.2 (can even root and install cwm).
after this i try again to upgrade to 2.3 official gingerbread, fist boot is fine, but when i reboot i get again stuck in bootloop... pls help
I am having the exact same issue, does anyone know how to fix this?
The problem is solved？
zgulia22 said:
The problem is solved？
Click to expand...
Click to collapse
I dont know for sure. I flashed another B528, same issues. Tons of FC messages.
I flashed an older B517, installed CWM, flashed DZO's excellent Aurora 5.0, and everything seems fine, for now.
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
r34l1ty7 said:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
Click to expand...
Click to collapse
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
123hiten said:
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
Click to expand...
Click to collapse
Just wanted to say a big thanks. Your solution worked a treat. :good:
I take it I can now root as usual? Nothing else needed? ...apart from not trying to be stupid again
I rooted my cousin's samsung galaxy tab 4 (sm-t330nu) afterwards I tried to install Root Browser but then the tab froze so I thought a simple glitch or something, so I turned it of. Then the bootloop happened. I tried factory reset, wipe cache, but none worked... I tried to get as much information like using odin, but I really don't know what to do. I tried flashing TWRP- T330.TWRP.2.8.3.0.img then I made it to T330.TWRP.2.8.3.0.tar.md5 using a tool, flash using odin v3.07, but i cannot boot into it. Tried using philz touch recovery but I think the version I used wasn't meant for the tab. This is my first time handling android so I really don't know much.
Can you guys post a simple step by step on how to use any recovery tool (CMW/ TWRP/ PTR/ etc) or any kind of way to fix this bootloop? I'm just frustrated spending three night trying to understand the whole procedures. I'm going to try doing a hard reset though. correct me if I'm wrong but does flashing a custom rom a surefire way to fix it?
Thanks in advance
nothing4 said:
I rooted my cousin's samsung galaxy tab 4 (sm-t330nu) afterwards I tried to install Root Browser but then the tab froze so I thought a simple glitch or something, so I turned it of. Then the bootloop happened. I tried factory reset, wipe cache, but none worked... I tried to get as much information like using odin, but I really don't know what to do. I tried flashing TWRP- T330.TWRP.2.8.3.0.img then I made it to T330.TWRP.2.8.3.0.tar.md5 using a tool, flash using odin v3.07, but i cannot boot into it. Tried using philz touch recovery but I think the version I used wasn't meant for the tab. This is my first time handling android so I really don't know much.
Can you guys post a simple step by step on how to use any recovery tool (CMW/ TWRP/ PTR/ etc) or any kind of way to fix this bootloop? I'm just frustrated spending three night trying to understand the whole procedures. I'm going to try doing a hard reset though. correct me if I'm wrong but does flashing a custom rom a surefire way to fix it?
Thanks in advance
Click to expand...
Click to collapse
I'm by no means an expert. I just dabble when there is something particular I want to do, but I had a similar problem earlier and managed to fix it using odin. I have the sm-t330nu as well and I was trying to move an app to the system apps folder. When I went to reboot I got the bootloop. I installed odin and flashed the same rom I had before and it solved the problem. Before you flash in odin your device needs to be in the correct mode. Press the power button then press home volume down and power button to get the download custom rom screen then press the volume up button to continue. That should take you to the odin mode download screen and from there you can flash in odin on your pc once odin has detected your device. Good luck!
Iaokim said:
I'm by no means an expert. I just dabble when there is something particular I want to do, but I had a similar problem earlier and managed to fix it using odin. I have the sm-t330nu as well and I was trying to move an app to the system apps folder. When I went to reboot I got the bootloop. I installed odin and flashed the same rom I had before and it solved the problem. Before you flash in odin your device needs to be in the correct mode. Press the power button then press home volume down and power button to get the download custom rom screen then press the volume up button to continue. That should take you to the odin mode download screen and from there you can flash in odin on your pc once odin has detected your device. Good luck!
Click to expand...
Click to collapse
Thanks for the advice! But what did you mean by "the same rom"?
go to twrp reboot settings, select bootloader and reflash via odin your device to its original stock rom. This will bring your device to its original settings without root and custom recovery. This is the solution I've done to my device. At least I can still use my device instead of other ways in trying to solve this custom recovery boot loop cause by incompatibility or no version of twrp made available to samsung galaxy tab 4.8.0 sm-t330nu.