Root dies not work - what am i doing wrong ? - Moto G Q&A, Help & Troubleshooting

I did everythig zo get root
I tried both solutions.
With the first solution ist just boots up but i dont get root
When i try the second solution with stock recovery everything works till i flash the img
Rocovery sucks vor more then 30 min during flash and so i restarted the phone
Now i flashed cwm and ist flashes the img but on bootup nothing happened
I tried to flash supersu1.43 and when i boot up then root works
When i try to start a root app it works but wehen i go to supersu app i wants to update system partition or something lije that and it sas that it wont take more then 5 minutes and i schould reboot the device or flash sonething with cwm
Supersu 1.43 zip is the latest Version
And my biggest problem is that after reboot root is gone
Its something softroot like thing ...
My devixe is a german 8gb from saturn
Thaks for helping
Sorry for my bad english and if i broke any forum rules
Sent from my XT1032 using xda app-developers app

And sorry for typing like ****
Im standing in a bus....
Sent from my XT1032 using xda app-developers app

Is your G encrypted?
If so, you are likely struggling with the same thing as I am: http://forum.xda-developers.com/showthread.php?t=2565063

New theory: the Moto Care Device Adminstrator might be at fault - could you try to turn that off?

Related

[Q] Stuck on Running exploit

i was able to s off mine using alpharevx but when i try to run gingerbreak i was stuck on running exploit for about 30 mins.. any tips on how am i be able to achieve root?
If it said something along the lines of it 'wasn't sure it worked' it should be ok and did work .Mine done that but phone was still rooted
Gosh... Just my luck... have managed to s-off, now stuck on gingerbreak as op.
had the same, but you can flash SU from the recovery now, so why bother with ginger break?
Same here, but when I formated the SD card and run the process again my phone was successfuly rooted
Sent from my HTC Desire S using XDA App
Valwit said:
had the same, but you can flash SU from the recovery now, so why bother with ginger break?
Click to expand...
Click to collapse
Do I need cwm for that? See, I've chosen 'n' at the end of s-offing process, as I am not planning any rom changes.
Try version 1.1 worked for me
Sent from my HTC Desire S using XDA Premium App
yerfdes said:
i was able to s off mine using alpharevx but when i try to run gingerbreak i was stuck on running exploit for about 30 mins.. any tips on how am i be able to achieve root?
Click to expand...
Click to collapse
My phone was done by hardware cycle clip a couple of months ago, first experience with Ginberbreak was confusing but it does work. First turn on debug mode, second turn off fast boot in power menu cos you'll need to fully reboot after the gingerbreak error.....
So run gingerbreak and after the SD card can be removed safely indicating the sdcard is now unmounted, then wait a couple of minutes and give the screen a few swipe another message error that it didn't work telling you to check for superuser in the app drawer. Do check if superuser is installed then you're rooted but no use without SD card access, now just reboot fully and check that sdcard is mounted then go to market download Rom manager and flash clockworkmod.
If no further luck then refer to loveboatcaptain's unsecured boot image might be easier stickied thread.
Sent from my HTC Desire S using XDA Premium App
bronx said:
Gosh... Just my luck... have managed to s-off, now stuck on gingerbreak as op.
Click to expand...
Click to collapse
... aaaand rooted.
Dunno how, but gingerbreak 1.20 have eventually worked for me.
Shweeeeet...

[Q] HELP xoom root!

ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App
Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App
What version of clockwork mod recovery are you using?
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.
flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.

[Q] HTC one X crashes during install, loops, van't do a thing

Oh dear this looks really really bad! I hope someone can help me
I tried to install Slim ICS on my HTC one X. So I did a complete wipe and then I flashed Device_x.x.zip***, and then Slim_Common.zip
But now my phone keeps rebooting and rebooting and rebooting. There is nowhere to go, even if I go to recovery and try to wipe again it goes straight back to the Slim install screen and it starts rebooting again :crying:
Does anyone have any idea how I can get out of this loop?
Desperate here
No nandroid?
Sent from my EVO using xda premium
I am afraid not. Stupid I know :silly:
Happens to all of us lazy people or when Ur excited to flash ;P. I know the one x requires a flash of a certain file in order to work are u installing the right one?
Sent from my EVO using xda premium
I think I did yes. I did everything according to the instructions. I did install custom roms on this device before. No problems then. Whatever I do now it keeps going back to the install screen.
I'd recommend you check the md5 for the Rom if it fails download it through Ur pc and transfer via recovery menu (if your recovery supports it)
Sent from my EVO using xda premium
Will try and report back!
Thanks
now this is interesting. I downloaded HTC One X all in one kit
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
I then flashed another recovery program and that one DID let me clear cache etc. so no more install screen! However....when I want to flash a zip from sdcard it says no such file! Sdcard seems empty but I am 100 % sure I did not format that!
So question now is how do I install when it's not on my sdcard. you were saying transferring though recovery but how do I do that. Mount USB storage does not work: unable to open ums 1unfile. Oh my...I need a beer
Well I give up! I am now going to try to unroot and get back to stock since you can install stock rom through USB. Flashing stock recovery works....I got that far Now I have to wait a few hours for the rom dowload to finish so I guess I am going to get that beer now. I sure hope I don't have to throw my phone out of the window tonight
My phone is locked again, RUU, and SDARD works. Sorry for the drama but I really thought I bricked my phone. I think I will leave it alone tonight......and start rooting again tomorrow
Lol its all good. Sorry for leaving haha mw3 lol and I don't have the one x I got the LTE EVO
Sent from my EVO using xda premium

[Q][HELP]Razr HD XT925 on boot loop logo

Someone help me please, i'm in panic here, i just bought this phone yesterday and now screud the phone, the issue is, i see one update available, 4.1.2, i was in 4.0.4, the i click for make the update via OTA, but when my phone reboots its stucked in motorolo logo boot loop, all the times restart when come to logo, i go in recovery make the wipe data user, wipe cache and continue the same problem, i entered in fastboot mode and flashed via RSD LITE the FW STOCK correct from my country (BRAZIL) but even with this conitnue the same problem, i dont know what i can make now, i tried search one way to make downgrade back to 4.0.4 but i get one error because it s one older version, and my phone dont is rooted and my phone is bootloader locked, please some1 help me solve this problem, for GOD.
And sorry for poor english, i'm from brazil and dont speak very well... i think i said all the info i have got but if want know others thing just ask, i'm waiting for any help, thanks
Any one help? all this views and no one can help? please guys, i'm almost crazy here, please help.
Wish I could help you I would try rsd lite again it should work use 6.1.4 and flash 4.1.2 good luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for repply, but i make it so many times, i tried flash all the roms stock from my career and from my country, brazil retail's, but only the last brazil retail, the last LATAN and the last rom from my career can be flashed without problem, but all the times when i flash is over and phone reboot it stuck in boot loop, when it come to moto logo it freeze for some moments then restart alone and begin all again forever, i dont know why it dont pass that logo or why it always freeze there, i have access to recovery and ap fastboot if this info can be for some help....
Did you check this thread http://forum.xda-developers.com/showthread.php?t=2707579
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for repply,
yes i see this post and almost all post i can find in xda and in the internet, and all i try in unsucceded =/ hope some1 can help me

tablet died after flashing blob for 6.0 android

Hello, i just got a shield tablet( ready to be disabled) with android 4.2.2 on it. I wanted to update it to 6.0 ( using http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 ) but right after i unlock bootloader and flash blob tablet powered off and dont want go back on again... any ideas?
Edit:
by "ready to be disabled" i mean urgent ota on here http://shield.bogdacutu.me/
is there any way for hard reset or something, i already tryed all key combination for 20+sec each ... but it should be somethink else then kill switch cuz it not even boot to system, just powered off right after blob was updated ..
What blob did you flash?
Is it possible you flashed the kill switch blob?
Sent from my SHIELD Tablet using XDA Free mobile app
An Droid said:
What blob did you flash?
Is it possible you flashed the kill switch blob?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
i have 2 same tablets, on 1st i flashed all ok, on 2nd i flashed same stuff, from " http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 "
but mby error was i write at 1st flash blob , saw its impossible cuz i didnt unlock bootloader, so i unlock bootloader and flashed blob after it again, it didnt give any errors or something, in console it shows just normal stuff and after tablet just powered off ( had ~ 40% battery when i start)

Categories

Resources