Related
I modified this post to recap the whole story. You can find the timeline development from the second post on.
My TAB is now bricked, it does not give any sign of life even after letting it charging for hours.
Not Odin or heimdall would recognize it to I cannot flash anything.
Samsung Mexico (where I am now) told me they cannot fix it because the mexican version has a different hardware configuration.
I also called Samsung US and they told me they cannot accept it, I should go back to china and repair it there (??).
I decided not to waste my time anymore on this, as it become anti economic.
(if anyone is interested in buying it as spare-parts, please let me know!)
what happened, for reference:
Chinese unicom GST p1000, previously flashed (and running) with success roto-JME.
I tried to flash JQ1 with bootloaders but ODIN failed at hidden.rfs. Since then I never manage to boot the tab anymore.
I then couldnt flash any ROM containing either hidden.rfs or movinand.mst, it would always FAIL. In order to PASS I had to remove these two from the flash, but TAB will hang at Samsung logo during boot (not sure if the reason for not booting is because of the missing files, or these 2 problems have the same cause, but are not related with eachother).
I tried a huge number of different ROMs, all give same results (even JME will fail at movinand.mst now)
in case you are wondering I already tried different computers, win and ubuntu, Odin and heimdall, changed USB cables, always the same problem.
Given the above situation (base ROM not complete and not booting + /data unmountable) I managed anyway to install Overcome and AF974, but they both hung at GALAXY TAB boot screen (the very first one) and keep rebooting every few seconds. (This is different from when it hangs at samsung logo - see above)
After this recovery started to report partition errors:
I cannot mount /DATA in either CWM or ADB , it says:
mounting /dev/block/mmcblk0p2 on /data failed: No such file or directory
indeed /dev/block/mmcblk0p2 does not exist.
I tried the flashing routine again, and new different partition errors came up
now the internal sd-card was not mountable anymore, instead it would read ext-sd as internal
I tried the flashing routine again, and it bricked completely to death
What I DIND'T do (learned about it too late!) prior to flash JQ1 was to neither ROOT or patch bootloaders before flashing, but I belive I should be ok:
I flashed JME successfully in the past and should be pre-rooted.
I also have reasons to think my bootloaders are not protected as:
I tried chainfire's SGTBootloaderCheck-1.0,it says I am clean.
I can flash CF-root, which is supposed to fail on protected bootloader.
I was brave and stupid enough to format /boot from recovery. Tab would not boot but I could flash it back from Odin with no problems (still, flashed an incomplete ROM without hidden.rfs)
i also tried other ROMS, but have the same problem with all of them
I tried chainfire's SGTBootloaderCheck-1.0 while on recovery mode, but it says I am clean
I cannot get out of this brick, can anyone point me in the right direction?
I'm not the one with the answers, but I casually saw these two posts hours ago:
How to unbrick tabs:
http://forum.xda-developers.com/show....php?t=1133590
This unlocks bootloaders so your SamFirmware.com rom won't brick you:
http://forum.xda-developers.com/showthread.php?t=888071
thanks but I have already seen and tried all of these.
The most commune solution to a soft brick in the forum is: "flash again".
but in my case it seems I just cannot flash anything.
Perhaps what I am looking for is a method/checklist to diagnostic the source of my problem?
or should I just keep trying flashing every possible rom? (i already tried at least 9)
2 cents
Hi,
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
thank you but I'd need more directions..
dirlan2001 said:
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
Click to expand...
Click to collapse
Thank you. this is a new approach and definitively worth trying it.
I would need more directions thou, as I only can flash roms using odin.
Are you saying I can flash this ROM from the recovery mode, I don't need Odin?
I am a bit confusing about the process: you are saying: 1) mount everything 2) format 3) flash.
1. What do you mean my 'mounting'?
when I go to my recovery mode i can see the option 'apply update from sdcard'. Is this what you mean by mounting?
2. Then format everything. what and how? you mean the SDcard? I am not aware of anything else I could be formatting. Please precise.
3. then flash everything.
how is flash different by Mounting, in this case? havent I already 'applyed' these files in step 1?
I am sorry if all these questions sounds idiot, I probably miss a lot of basic knowledge. I swear I did my homework, I spent DAYS reading all the forums. It's just hard to catch up everything from stratch without help.
thank you!!
i think i got it
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
Hi,
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
After reboot you should have a newer CWM that has more options to it. Note that the reboot may take some time... Then you can use the 'mount' to get all partitions mounted r/w... Then you run the kernel.zip and the ROM.zip from 'install zip from SD | go to external SD | choose the kernel.zip // redo the same for the ROM.zip without rebooting in between'
jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
This sounds like you are in stock recovery and need cwm installed again.
________________________
Sent from my DROIDX X
dirlan2001 said:
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
Click to expand...
Click to collapse
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
jacopo3001 said:
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
Click to expand...
Click to collapse
On second thought, it may even be better to install the Overcome kernel first. That has the most recent version of CWM build in, and it makes your device ext4 instead of the old RFS. After that you easily can flash AF974's combo via CWM, whitout need to rename/copy anything. The link provides the guide to the mirror of OC, as their website isn't working anymore...
dirlan2001 said:
it may even be better to install the Overcome kernel
Click to expand...
Click to collapse
I have tried to flash GB-Stock-Safe-v5 (as for Overcome's docs) with Odin but it fails, just like all the other flashes I tried.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
jacopo3001 said:
I have tried to flash Overcome with Odin before but it fails, just like all the other flashes I tried in this period.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model：GT-P1000
CMIIT 10 2010CP4950
Click to expand...
Click to collapse
Hi,
WCDMA is the 3.5G data-line : this means, it's NOT the WiFi alone version. If it's marked as P1000 just as is, then it's the GSM version. That means, you have EDGE/GPRS quadband @ 850/900/1800/1900 Mhz and HSDPA 7.2Mb/s=HSUPA 5.7 Mb/s triband @ 900/1900/2100 Mhz ...
Hmmm, what error did Odin give out when the flash failed ?
BTW, happy newyear etc ...
dirlan2001 said:
BTW, happy newyear etc ...
Click to expand...
Click to collapse
Happy new year to you, and that you very much for your help!
dirlan2001 said:
Hmmm, what error did Odin give out when the flash failed ?
Click to expand...
Click to collapse
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
here is how it looks like when I try GB-Stock-Safe (recommended by Overcome) for example:
Code:
<ID:0/018> Firmware update start..
<ID:0/018> boot.bin
<ID:0/018> cache.rfs
<ID:0/018> dbdata.rfs
<ID:0/018> factoryfs.rfs
<ID:0/018> movinand.mst
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I remove these files (Hidden.rfs or Movinand.mst) from the TAR i can flash with no errors, but the tablet wouldn't boot.
This apply to EVERY Roms i tried so far, with no exclusion.
I am making up a new theory: the first bricking error happened after I flashed JQ1, which has bootloaders. Could it be that those bootloaders go in conflicts with the chinese version of hardware, and thefore the brick?
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
jacopo3001 said:
Happy new year to you, and that you very much for your help!
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
Click to expand...
Click to collapse
Hi,
No thanks, you're welcome LOL
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Cheers, and good luck
dirlan2001 said:
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread.
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Click to expand...
Click to collapse
thanks, I know those threads already (read them all!)
the main problem I don't get about the bootloader fix is that chainfire released a APK, which assume you can boot the phone!
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
regarding AF974, that's not my priority, I am just trying to have this thing working again..
jacopo3001 said:
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
Click to expand...
Click to collapse
Hi,
He did a 200 mile trip to have the MoBo changed .. LOL That doesn't help you any further I guess...
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
PS : as long as you can get it in download mode (odin) or CWM it's not a brick, it just not booting completely...
dirlan2001 said:
Hi,
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
Click to expand...
Click to collapse
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
jacopo3001 said:
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
Click to expand...
Click to collapse
Hi,
Do I understand correctly your system is up and running again ? In that case I would certainly recommend to run the complete guide to make it first stock again. The kernel indeed does a conversion to ext4, which is a way better filesystem as the rfs from Samsung. Look in the Overcome thread for the mirrors as OC seems still to have serious problems with their serversystem.
And if you take courage (and the habit) you might start looking for a more recent kernel and ROM...
dirlan2001 said:
Do I understand correctly your system is up and running again ?
Click to expand...
Click to collapse
The system is NOT up and running.
It's hanging at the Samsung logo.
But I can at least get to both download and recovery mode.
What happens is that, regardless which ROM I try, I cannot flash neither hidden.rfs nor movinand.mst (depending on Rom's content), they always FAIL on ODIN.
If I flash a ROM removing those 2 it Odin would success, but the tab will not Boot and hang at Samsung logo.
That's why I say the system is not stable now, I am not sure whether it's a good idea to go into changing FS now or would it screw up things even worst...
Phone won't boot past Galaxy Note Boot image
Phone will go in download mode by pressing Vol-Home Power buttons
Phone will go in recovery menu by pressing Vol+Home Power buttons but if i try to flash anything it shows verification error.
Anything flashed with Odin, goes successfully without any errors, but phone still won't boot past Galaxy Note boot image. When connected to PC in Odin mode USB recognised, when connected to PC with Galaxy Note boot image, USB not recognised (malfunctioning error appears)
I tried flashing ics/gb stock roms, kernels, pit files, and nothing helps
Please help
lastly
HAVE FLASHED N7000DDLC1_N7000ODDLC1_N7000DDLC1_HOME.tar.md5 using pc odin 3.04 and still stuck on gnote boot image
and lastly updated with :: N7000XXKL3_N7000ODDKL1_N7000DDKL1_HOME.tar.. but to no avail..
please help
do you have a custom kernal on such as hydroacore if you do or can try wiping cache and dalvic and factory reset then try reflashing if using pc maker sure kies is installed but dont use it use odin to flash a stock rom
anubis1126 said:
do you have a custom kernal on such as hydroacore if you do or can try wiping cache and dalvic and factory reset then try reflashing if using pc maker sure kies is installed but dont use it use odin to flash a stock rom
Click to expand...
Click to collapse
actually was on the stock ics and tried to install kingdroid by CWM.zip
and wiped data and cache from touch/temporary cwm..
then after install it got stuck on the first screen...
since then have tried to flash stock ics / gb firmwares but not getting past the first screen
first of all, make sure you don't make some foolish steps in wiping your phone., secondly, try to uninstall cmpletely PC kies and reinstall it again after. Once you've reinstalled that, don't open it, just open PC ODIN and try to boot back your phone in download mode. Make sure you have a yellow box on COM:1 in ODIN and use an extracted stock GB tar file and start flashing again.
EDIT: Since you've just mentioned you already wipe data in stock ICS.. are you using a safe kernel when you did the wiped?
if not, you may have toasted your Note.. imho...
it can take 5 to 10 mins after install to start however if it still goes no further and you can get into recovery can you flash any custom kernal,if you can do so then wipe and try to reflash if not i would ask dr ketan as he is awesome and may be able to help
^ No need to wait for that, as OP has already done a stupid thing of wiping on a touch CWM.. something that shouldn't be done at all....
only thing he can do is go to the section for the pit method partition to revive his phone... that's it!
letters_to_cleo said:
first of all, make sure you don't make some foolish steps in wiping your phone., secondly, try to uninstall cmpletely PC kies and reinstall it again after. Once you've reinstalled that, don't open it, just open PC ODIN and try to boot back your phone in download mode. Make sure you have a yellow box on COM:1 in ODIN and use an extracted stock GB tar file and start flashing again.
EDIT: Since you've just mentioned you already wipe data in stock ICS.. are you using a safe kernel when you did the wiped?
if not, you may have toasted your Note.. imho...
Click to expand...
Click to collapse
i was using the temp cwm used to gain root to flash .. very stupid i know..
my recovery and download modes are accessible so is my phone toast..
and if yes it is toast .. how to recover ??
letters_to_cleo said:
^ No need to wait for that, as OP has already done a stupid thing of wiping on a touch CWM.. something that shouldn't be done at all....
only thing he can do is go to the section for the pit method partition to revive his phone... that's it!
Click to expand...
Click to collapse
since i do have warranty on my phone left for another 2 months should i give it to the samsung repair center ?? what will they repair and how much time is expected it to repair ??
I suggest you ran first the partition scanner from here: http://forum.xda-developers.com/showthread.php?t=1823918, see if your partition don't have one of those bricked blocks....(courtesy of hg42)
Also consider this link - http://forum.xda-developers.com/showthread.php?t=1667886 for the pit file method
letters_to_cleo said:
I suggest you ran first the partition scanner from here: http://forum.xda-developers.com/showthread.php?t=1823918, see if your partition don't have one of those bricked blocks....(courtesy of hg42)
Also consider this link - http://forum.xda-developers.com/showthread.php?t=1667886 for the pit file method
Click to expand...
Click to collapse
but sadly the stock recovery is not accessing my memory card files and only internal sd and it has no option to mount storage ..
how to access the files i put in my memory card.. or should i flash some other ics stock rom as they have more options in stock recovery ??
no need to aggravate the problem by flashing another ICS... your Note's been bitten already.. don't let it bite twice...
Your last rom flashed is KL3 then have you wipe cache and data from recovery?
If not then do it, it should boot then.
Make sure last rom was flashed correctly and u are currently on KL3
If you have to press home button in recovery to enter your choice then it should be gb (kl3)rom (on ics you need to press power to select)
If wiping cache and data also not work, then flash wipe version of gb rom. If it stuck at data.img then yu have got damaged and should send to service Centre, without doing anything
Sent from my GT-N7000 using xda premium
When my phone boots it only gets to the samsung logo
I am able to use the recoverymode and downloadmode.
Wiping data won´t work. Wiping cache works.
Can´t flash a CustomROM from my SDcard through CWM
I was able to connect my phone to the PC. ADB finds the phone but adb shell won´t work. (No such file or directory <2>)
How can I install either a regular Androidversion or a CustomROM now.
found this but only for Galaxy S3, so the files won´t help me
http://forum.xda-developers.com/showthread.php?t=1840030
Hope you can help me
Tobias
Download a Stock Rom from sammobile.com or one of the prerooted Roms (I always use a GB LC1 from bodivas for this) and install it with the PC version of Odin.
tried that, Odin stops at "NAND write start!!"
AW: Softbrick N7000 Need Help
What Rom did you have and what did you do before this happened?
Sent from my GT-N7000 using xda premium
Now I used a regular Android 4.0.4. ROM
Before that I tried with a 2.3.1 ROM. This is probably the reason for the trouble, isn´t it?
Tobias H. said:
tried that, Odin stops at "NAND write start!!"
Click to expand...
Click to collapse
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
ThaiDai said:
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
Click to expand...
Click to collapse
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Did you use cwm.zip?
To use with Odin? No
When I started it from the regular Android Recoverymode? Yes
Don´t you think this might be exactly the problem I have?
http://forum.xda-developers.com/showthread.php?t=1840030
Tobias H. said:
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Click to expand...
Click to collapse
Why did u buy SGN? To brick it?
Do you even read and search before doing something for the first time?
LOOK, READ AND LEARN THIS for stock ROMs and kernels, specialy for ICS:
- http://forum.xda-developers.com/showthread.php?t=1424997
-http://forum.xda-developers.com/showthread.php?t=1371007
-http://forum.xda-developers.com/showthread.php?t=1827394
To run ur device find something and READ.
Try leaked JB custom ROM and stock rooted kernel with safe emmc_cap_erase block (emmc bug fix) -Philz Kernel
READ and LEARN.
Have fun
P.S. Maybe you will need our friend hg42 and his famous .PIT files so here it is: http://forum.xda-developers.com/showthread.php?t=1667886
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
synthecypher said:
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
JJEgan said:
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
Click to expand...
Click to collapse
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
synthecypher said:
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
Click to expand...
Click to collapse
All depends upon the package but most CWM are root and recovery .
TRYhttp://forum.xda-developers.com/showthread.php?t=2002953
Ended up using Auto-Root which seemed to work no problem.
synthecypher said:
Ended up using Auto-Root which seemed to work no problem.
Click to expand...
Click to collapse
I initially had a rooted stock ROM that i was using for ages then upgraded to a custome ROM but for personal reasons decided to go back to stock.
Loaded stock ROM with intention of rooting only to get rid of bloatware, but not one of the ODIN Flash recoveries work at all, not one, so like you ended up using CF Auto and that worked but now im still stuck with Stock Recovery. I dont understand why none of the recoveries flash when they did before.
Cheers
trouble with cwm/ twrp
Hi all. Yes I'm a noob and I wouldn't ask If hadn't tried a plethora of ways to install either cwm or twrp.
It took me a good hour to find this thread so hope I'm in the right place.
Ok I used odin to root and cwm didn't stick so still on stock rec. However I used framaroot to get super su working and titanium says I'm all rooted up. Other apps only for root also work.
I've since tried using goo manager and Rom manager to install cwm or twrp and both say unsupported.
I've searched these here threads and found a few with same problem namely when using odin cwm wont stick and android reinstalls stock recovery.
So I'm a bit stuck, I'm rooted but have no cwm or twrp.
Any help would he much appreciated.
Try Philz recovery .
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
thanks !
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
Click to expand...
Click to collapse
Thats exactly how I understood the cwm not sticking problem. I have tried rom manager and said not compatable with my device as did goo manager for twrp. I think odin is the only way I get it to stick. So il flash in odin and il try to get into cwm as it boots and wipe those two files you mentioned.
But then can I just boot up as normal ? or will android try to reflash its stock rom ? Damn my phone for being so difficult
I only ask because I haven't decided what CR to use yet (or even looked for any). I was gonna get it all ready first then learn how to install a CR - 1 thing at a time i thought.
Anyway thanks for your help :good:
JJEgan I found Philz thread to be helpful but something I feel Im just not ready for. Im new to this and although the updated cwm looked cool there were just to much going on, maybe for a later day.
Thanks all the same :good:
wiping data plus cache plus dalvick cache is done to prepare your phone for the custom rom that you are going to flash. the wiping is to clean those partitions because if they are not erased you will have problems. especially if you go from one android version to another or touchwiz to aosp. it is done so you get a clean install with minimal issues. if it is not done you will most likely bootloop. effectively it is a factory reset. all of your apps and app data will be gone so you do not want to do that unless you have backed up your apps . however sometimes google automatically installs them after you sign in.
I am not sure why clockwork mod does not stick but if you copy the rom you want to your phone install clockworkmod with odin and then use clockwork mod to flas the rom and gapps package then factory reset you will not have the stock recovery anymore. but this has to be done without booting into android stock . PLEASE FOLLOW THE FLASHING INSTRUCTIONS TO THE BEST OF YOUR ABILITY. AND UNDERSTAND ANYTIME YOU FLASH OR MODIFY YOUR PHONE YOU VOID YOUR WARRANTY AND POSSIBLY CAN CAUSE IRREPARABLE DAMAGE. BEST OF LUCK!
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Also philz recovery is highly recommended
HERE IS SOME VERY GOOD READING http://forum.xda-developers.com/showthread.php?t=2362743&highlight=philz+recovery http://forum.xda-developers.com/showthread.php?t=2344125
think I got it lol
Ok that's sounds good. However I've just read the threads you linked and now I've got to back up my imei and NV files first or il loose them when flashing. The procedure is all there and seems doable for a noob but i read some peeps are having trouble just doing that. I really wanted to root/install a CR regardless of the troubles cos I want full access and more importantly want to learn all the ins and outs so I can get the best use from my phone so glad I found this forum cause I'm sure I would have bricked my phone otherwise.
Might I ask if I've got this right tho?
1: backup imei/NV files
2: use odin to get cwm to stick using your method
3: boot into cwm to wipe data/dalvick cache and gapps
4:use cwm to flash a CR
5:factory reset
I think that's right?
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
i had the same Problem before.
I Just disassembled the battery after a full-wipe for few minutes and it works... i don't know y, but that was the only way... ?!
brilliant thanks!
ashraf sharif said:
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
Am I backing up to ext SD card?
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
Are these seperate zips?
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
Click to expand...
Click to collapse
Thank-you for all that,I really appreciate it.
Can I ask the difference between the apps nandroid manager and titanium? I've backed up with both and wondered if i really needed to? The nandroid backup was nearly 3gb!
Also I was gona backup with qpst for imei and NV files but then read its only for US versions? Will the backup of efs folder include those?
honestly i really dont know what the differences are. l do not use custom recoveries or custom roms. i dont use titanium backup .Any rom I flash i get from sammobile.com. one reason i do not use custom roms is that none can support mhl. I use a monitor and bluetooth mouse and keyboard . without mhl I cant mirror my screen so i always stay with stock roms. i use Xposed framework for modifications.
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone......
Click to expand...
Click to collapse
thx you so much. this was the secound s3 that had this issue. deactivating auto reboot did the job!!!!
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/
Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan