Hi, I have a sm-p900 (wifi only), it is rooted and I have been running the Gigawatts Pro rom for several months. I have an older version of Twrp and decided to update it to the most recent one, 2.8.1.1 from http://techerrata.com/browse/twrp2/v1awifi. I installed it using odin and it seemed to install fine. I made a nandroid back up and it backed up all partitions and did an md5 generation, but on the last partition (system) the screen hung up on md5 generation. I waited a long time and the details seemed to indicated that the back up had ended, but it still had the updating blue bar on the bottom and the "md5 generation" title on top. The only way that I could back out was to power off and back on. I even tried installing a lower version 2.8.0.0, but had the same problem. Any thoughts? Never ran across this before, couldn't find it when I searched either. Thanks in advance for any help.
Related
Alright, I have a verizon GS3 I rooted it about a year ago and installed AOKP. Back in october i switched to CM without any problems. About two weeks ago or so, a CM 11 M3 update came through the automatic updater in CM so i figured i'd give it a shot. I installed it and it boot looped. So i figured it was just messed up went back to CM 10.2.1. After i went back to 10.2.1 i immediately got "xx app has stopped working" for almost all of my apps upon booting. Then i figured out what might have been wrong when i switched to CM 11 M3 and flashed the new gapps, well it still boot looped. So then I flashed a recovery (which was AOKP) that I made back in October and the phone was fine, until last night when I was at work and the battery died. After i got it on the charger and went to boot it up it started boot looping.So i went to try and flash the recovery again to see if i can salvage anything but i get an MD5 mismatch error when i try to flash any of my recoveries. I tried advanced system recovery as well and i didnt get an MD5 mismatch error but it just went back to boot looping. I have very basic knowledge of rooting and flashing ROMs and i've looked around the web quite a bit to see if i could find a fix but i havent found anything. Any help would be appreciated. Thanks
BobbyTam said:
Alright, I have a verizon GS3 I rooted it about a year ago and installed AOKP. Back in october i switched to CM without any problems. About two weeks ago or so, a CM 11 M3 update came through the automatic updater in CM so i figured i'd give it a shot. I installed it and it boot looped. So i figured it was just messed up went back to CM 10.2.1. After i went back to 10.2.1 i immediately got "xx app has stopped working" for almost all of my apps upon booting. Then i figured out what might have been wrong when i switched to CM 11 M3 and flashed the new gapps, well it still boot looped. So then I flashed a recovery (which was AOKP) that I made back in October and the phone was fine, until last night when I was at work and the battery died. After i got it on the charger and went to boot it up it started boot looping.So i went to try and flash the recovery again to see if i can salvage anything but i get an MD5 mismatch error when i try to flash any of my recoveries. I tried advanced system recovery as well and i didnt get an MD5 mismatch error but it just went back to boot looping. I have very basic knowledge of rooting and flashing ROMs and i've looked around the web quite a bit to see if i could find a fix but i havent found anything. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Try and odin back to stock if your back ups are on the sd card.
Hi there, I'm not feeling very cluey right now.
I finally got around to trying a custom ROM, I went with the latest one @daniel_hk had uploaded which was Slim-p6810-4.4.4.build.7.2.1-UNOFFICIAL-20140816-1116.
I used the cwm-6.0.2.3-p6810.tar recovery.
I had been using the official ICS ROM from a long time ago, it mostly worked fine for me but an app I've started using recently says it really wants a newer version of android.
Before flashing it I took a backup.
Having used the SlimKat for a bit I found a few things I wanted to work didn't and the colour inversion thing was getting to me so I tried CARBON-KK-UNOFFICIAL-20140912-1616-p6810 to see if it would work well enough for me. It has the same Bluetooth problem but I haven't had the screen inversion problem.
Before trying the second custom ROM I also took a backup. I also took a backup after setting up the Carbon ROM so I wouldn't have to do it twice!
Somewhere around here I noticed that my Winblows 7 PC wasn't recognising the tablet anymore, it also was charging slower than it used to.
Wanting to go back to the ICS ROM I was using originally I booted into recovery and went to restore it and here's the problem.
It isn't there to restore.
The other two backups I made are there though.
I was going back to ICS to see if Winblows would detect it again, although I'm starting to suspect that the USB board in the tablet might be faulty now. Windows says that the device has malfunctioned so it doesn't recognise it, I've tried numerous different versions of the USB driver. I remember Winblows update saying it had a newer version of the Samsung Android drivers and let it update them, this may have been a mistake.
So how do I restore my ICS backup, I think I recall there being a file system change when they added the multiple accounts on a device patch, 4.3 I think, so is that part of my problem?
I've also tried using twrp-2.8.0.0 and discovered that it can't use the CWM backups and I then flashed cwm-6.0.4.5 to see if the newest version would help me. Still no dice. As my tablet won't talk to my PC I flashed that with Mobile Odin Pro, I'd avoided buying that as I will probably be getting a Sony Z3 Compact Tablet and Odin seems to be a Samsung only thing.
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
Brief back story goes like this. Working TF300T running JB, was running slow and laggy so it seems a good time to flash something new. I'm no android/linux pro but I have a good base knowledge (you may question this statement later) . Successfully unlocked and flashed CM12 and TWRP. Tablet ran ok, sometimes significant lag, updated to a few different nightlies, then eventually decided to go back to stock. This is where it all went wrong. I followed the instructions here on XDA by d_crossfader. The flash seemed to go as expected, wiped cache/dalvik, rebooted. Loaded up to stock JB but no wifi, rebooted, all went bad. Stuck at the silver ASUS with spinning dots screen.
here's what working at this point.
I can load to fastboot, recovery etc, and have re-installed TWRP, the latest 2.8.1 failed install, but 2.6 is working (since I've read that this rev has issues).
I went back to the CM12.1 ROM I had working and it seems to flash fine but GAPPS fails, gives 'E: error updating binary in zip' for /boot and /recovery.
I think I've exhausted my abilities so it's time to call in people with actual skills.
What should my next move be? I'd be happy with stock or custom ROM's just like to get it back to functioning.
Thanks
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
MI MIX 3 8/256
Stable 10.3 Chinese ROM with twrp (10.2 before update, with root and twrp)
Had no root but unlocked bootloader
z1ldj1an said:
Good day,
Help is needed..
I flashed TWRP on the phone since it was not long ago updated to version 10.3 (China).
It flashed well (without errors).
The reboot was successful. No data was lost.
In the morning I decided to check the email, turned on the WIFI, and it went off after 2-3 seconds (everything was OK in the evening, it worked like usually). I thought that restarting the phone would fix the flaw, but alas, I was stuck in BOOTLOOP. Starts with the Mi. LOGO, then goes out, then shows again and goes into Recovery. Recovery runs. All data can be accessed. Restarting is possible only into RECOVERY and FASTBOOT.
What could be the snag here and how to solve it?
P.S. Have tried 'dirty flashing' 10.3 and 10.2 versions from TWRP, changing the kernel (androplus 7-9), reflashing Magisk (recommended by some users on a russian forum), recovering the boot.img (since it it the only recovery I have got).. All that to no avail.
Bootloader was always unlocked since I bought it and rooted. It was MIUI v10.0 then.
Click to expand...
Click to collapse
Back up, wipe, flash, restore
Ok. That was the one thing I tried to avoid, since my backup is 27G (nandroid) and internal storage is 133G..
Will try and feedback.
Hi all,
Got it back again, of course with all data and apps gone. I have done nandroid backups (since there is no other way of backing things up from TWRP, except copying everything) from recovery before starting the upper described process. I figure they are of no use to me now or are they?
Please advise
P.S. restoring from nandroids brought me back to square 1..
z1ldj1an said:
P.S. restoring from nandroids brought me back to square 1..
Click to expand...
Click to collapse
Something not right with your data so start over
Restarted, redone. Recovered only Data. Looks ok but works a little laggy..
Upd.: needed to set up the screen lock after had done that and a restart, all works like it was, except with a new OS version
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Isopropil said:
Install TWRP from xiaomi.eu, the official one from here seems to be a lot more buggy.
Click to expand...
Click to collapse
I took it from twrp themselves, not bothering to search any forums. It's not like digging for gold or the like
Upd.:
I read that the official TWRP doesn't support some mounts migrating from EU to global or CN-->EU V Global. It was discovered that it has some bugs with mounting paths. People recommend the LR Team TWRP over the official because of that, besides it has more options under Advanced tab e.g.
Personally I prefer the one that does the job for the moment and is the latest, so it was an easy choice for me ? especially installing a fresh OS update.