Hi! I am unlocked my nexus one and now tried to root it.
I tried with Win XP and Win 7 with the same result.
I can see the device. If i go to the command promt and enter
"adb devices" it shows me the serial - So, usb is not the problem.
I also successfully unlocked it the same way.
Dev. Mode USB is also activated.
As soon I try to root it i.e. with superboot, Android SDK etc. I get the message
"waiting for device" (stays there for ever)
also when I want to lock the device again - same result.
Something must have happened preventing me to access the phone.
Also did a hard reset - without success.
Bottemline I am STUCK. The phone works, but no root .
Versions: ERE27 with 2.1update1
Someone an idea?
Thanks
Try a different USB Port. You can't relock the device.
MatMew said:
Try a different USB Port. You can't relock the device.
Click to expand...
Click to collapse
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Oh really?
Can you provide link proof on how to re-lock the bootloader?
Lol - he thinks you can "re-lock" it.. hahaha..
did u debug ur usb....?
helipilotx said:
Well I tried already on different PC's.
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
pjcforpres said:
I think this may qualify for post of the year!
Anyways, why are you even trying to root the stock ROM? Flash a custom ROM, already rooted, with the high memory kernel. As great as the stock ROM is, rooting really doesn't do anything unless you want to mess with the stock ROM... but that is like buying a V8 conversion for a Fiat, then only running 4 of the 8 cylinders.
Click to expand...
Click to collapse
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
You have to install the correct adb drivers
http://forum.xda-developers.com/showthread.php?t=613217
Eclair~ said:
Lol - he thinks you can "re-lock" it.. hahaha..
Click to expand...
Click to collapse
glad ur soooooooo much smarter
congrats ! A+
helipilotx said:
Well, how ever - I'll might be wrong, just saw someone do it on you tube (might was fake)
Anyway, well it does not matter whether I want to root the stock rom or flash a custom rom - my point is it always shows me
"waiting for device"
Click to expand...
Click to collapse
can you post the video link
helipilotx said:
glad ur soooooooo much smarter
congrats ! A+
Click to expand...
Click to collapse
Out of all the people that basically implied, or thought, what I said you - had to have a 'comeback' to me.. guess its because I said "hahaha," and "lol". If we really could re-lock the bootloader though... i'd be all over that..
TFJ4 said:
You have to install the correct adb drivers
Sorry, this is not the problem. These drivers I downloaded and installed already
As I said I can see the device and was able to unlock it.
- Any other ideas?
Thanks.
Click to expand...
Click to collapse
chronzz said:
can you post the video link
Click to expand...
Click to collapse
Have to look for it again. I saw it on my research to solve this problem I am having. When I find it again i will let you know for sure.
Anymore ideas anyone?
Thanks!
I had this problem yesterday (my first ever ROM flash!). I'm sure you didn't make this mistake, but my phone had to be on the boot (white) screen before it was recognized. When the phone was turned on normally, or off normally, I got the "Waiting for device" message.
FYI: I'm using Linux Fedora Core 12 on my PC.
Just had this problem. Jade this stupid mistake of not doing it while on the bootloader screen.
helipilotx said:
but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
That is THE best post i've ever read... just see the confidence
Perhaps the video he saw was of a holiday phone, in which case
Code:
fastboot oem lock
does work.
No good on our retail ones (yet) though.
helipilotx said:
FYI - It's not majorly important here, but yes you can re-lock it - The same way you unlocked it.
Click to expand...
Click to collapse
Love this post!!! +1 for post of the year!!!!
Related
So this has been mind breaking for me. I failed to flash the blackrose hboot everytime i trie and on every rom. It gets to the point where it has sent it files and then it says <waiting for device>. This happens on stock, BuglessBeast, rcadsmixhd 2.3 & 1.6 and hypersense (i like sense ). Anyone has any advice . Btw it did not brick it.
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
m0_t3 said:
the problem your having isn't actually related to which rom your using on your phone. its that its not being detected as an adb device. you need to make sure that your drivers are installed and you see it in device manager as an ADB interface under Android Phone.
Click to expand...
Click to collapse
Ehm, usb debugging is enabled and detected by the software at first. It gets to the point that it sends its hboot and after that it says something like error: deviceoffline and then stuck on waiting for device forever.
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
m0_t3 said:
it could be that another program like PDAnet is interfering.
do you use any other programs on your PC that would use adb?
Click to expand...
Click to collapse
well maybe htc sync but that was closed and its process was killed by taskmanager. No other programs i can think of.
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
m0_t3 said:
well if your drivers are fine and there is nothing causing some form of interruption then. its probably an issue coming from the phone.
since you've tried it with so many different roms am guessing you didnt bother running/installing any apps
try it without the SD card inserted maybe.
thinking i should try and see if i can't replicate your issue find out what the issue is.
Click to expand...
Click to collapse
SO without my sd card it did not make any difference, apart from that it now mixes the message: adb server is out of date. Killing... and then waiting for device again.
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
m0_t3 said:
the first time i installed blackrose i didn't use this method but maybe you can try flashing the hboot manually, which is what i normally do now, find it more straight forward.
[edit]
is your bootloader unlock?
Click to expand...
Click to collapse
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
m0_t3 said:
http://forum.xda-developers.com/showthread.php?t=1270589
download the manual version zip file from there. the instructions are contained inside the zip.
he removed the caution about slcd N1's so i think that shouldn't be a problem anymore.
Click to expand...
Click to collapse
WOW you are awesome sir thank you now it works i wish you could click the thanks button 30.000 times.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Awesome.
Glad to help ^_^
Sent from my Nexus One using xda premium
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
bassmadrigal said:
You can easily flash ROMs without unlocking the bootloader. All that is required is to root the original OS and install a custom recovery using a program like ROM Manager.
But I believe the phone is detected differently when in fastboot mode. Did you verify that the phone is still properly recognized in device manager when in fastboot mode?
What happens if you put the device into fastboot mode (holding the trackball when powering on) and you type fastboot devices at your command prompt?
Click to expand...
Click to collapse
It gives me attached device: Ht9 and thencq lot of numbers
Sent from my HTC Nexus One using XDA App
race55 said:
It gives me attached device: Ht9 and thencq lot of numbers
Click to expand...
Click to collapse
Well, that definitely means that your device is recognized. Did you get it working?
bassmadrigal said:
Well, that definitely means that your device is recognized. Did you get it working?
Click to expand...
Click to collapse
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
race55 said:
Ehm using manual method it worked. It was kinda confusing because in the blackrose thread it says that u must use manual for osx. He should update his post
Click to expand...
Click to collapse
If you throw a post at the end stating what you had to do, he would probably update his original post.
Not directly related but I had to use BREditor and create a new hboot with the 200/16/220 layout and flash that. I just could not get the ICS roms to flash otherwise... strange...
Click to expand...
Click to collapse
ICS is too big for the stock ROM space on the N1, so you need to make those alterations so it can fit. texasice did make a striped down version that works on stock though.
race55 said:
Ehm obviously yes how i can flash roms other wise? How do i flash this hboot then. BTW i have slcd nexesus one phone if that matters
Click to expand...
Click to collapse
If you are like me, you have been flashing ROMS on your phone for years before you ever unlocked the bootloader. I didn't do it until about 6 months ago because I needed to flash Blackrose. Also, don't bite the hand that is trying to feed you.
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)
Hi, I have recently purchased a Nexus 6 in order to root it & to be able to flash custom ROMs. I am basically a newbie to Android so please go easy on me. After a failed attempt to gain root access the OEM unlocking option in developers settings is greyed out and cannot be switched on. USB debugging is working. Can anyone help me to turn it all back to normal? I have tried to reset it to but its still greyed out. I have a feeling I have to work it with Commands but not really sure how. Any help is appriciated. Many thnaks.
Is your bootloader unlocked?
You don't need to root stock to flash a custom rom, why would you?
You should check out, if the booloader of your devices is already unlocked.
You can see it, if you start your phone and you see an open lock at the bottom of the start-screen (attachment)
So if the bootloader is unlocked, you have to flash a custom recovery like TWRP to flash a custom ROM.
(Others ways are possible but more difficult)
A very good guide is here:
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
MartinN6 said:
You should check out, if the booloader of your devices is already unlocked.
You can see it, if you start your phone and you see an open lock at the bottom of the start-screen (attachment)
So if the bootloader is unlocked, you have to flash a custom recovery like TWRP to flash a custom ROM.
(Others ways are possible but more difficult)
A very good guide is here:
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Thanks I have followed the thread before and managed to unlock the bootloader without any probs however I can't get twrp onto the phone at all so there fore I can't get access to the root. Always get some error. Might be because I'm using a Mac and most of the tutorials i have found online are for Windows users (my windows 7 laptop is painfully slow)
scherk said:
Thanks I have followed the thread before and managed to unlock the bootloader without any probs however I can't get twrp onto the phone at all so there fore I can't get access to the root. Always get some error. Might be because I'm using a Mac and most of the tutorials i have found online are for Windows users (my windows 7 laptop is painfully slow)
Click to expand...
Click to collapse
Hello,
This is weird, I have found a lot of tutorial for Mac:
https://www.google.fr/search?q=adb+...57j0.9254j0j4&sourceid=chrome-mobile&ie=UTF-8
I guess at least one of them should work... :good:
Good luck...
5.1 said:
Hello,
This is weird, I have found a lot of tutorial for Mac:
https://www.google.fr/search?q=adb+...57j0.9254j0j4&sourceid=chrome-mobile&ie=UTF-8
I guess at least one of them should work... :good:
Good luck...
Click to expand...
Click to collapse
Nice one. I do know how to use Google man :laugh: will have a look about again once I have some time to spare :good:
scherk said:
Nice one. I do know how to use Google man :laugh: will have a look about again once I have some time to spare :good:
Click to expand...
Click to collapse
Hey,
Some people tend to forget it is the most reliable source of information yet. :good:
Good luck...
Hi,
someone know whats is the good DSU to used with RMX3311 under RMX3311_11_C.10
and also what is the différence between all versions ?
ludoverblog said:
Hi,
someone know whats is the good DSU to used with RMX3311 under RMX3311_11_C.10
and also what is the différence between all versions ?
Click to expand...
Click to collapse
If you have locked bootloader, don't use it! You will hard brick your device.
daniml3 said:
If you have locked bootloader, don't use it! You will hard brick your device.
Click to expand...
Click to collapse
tow late, but i didn't remenber what is the native
I fail to see how this bricks the phone, it's a dynamic image
On my phone it literally loads a virtualised android which I can stop with a restart
I was curious once and launched the one I circled in the photo
I don't think you should brick it any more than I did but it's probably not a Virtual Machine you're looking for ^^
Obsessed Tweaker said:
I fail to see how this bricks the phone, it's a dynamic image
On my phone it literally loads a virtualised android which I can stop with a restart
I was curious once and launched the one I circled in the photo
I don't think you should brick it any more than I did but it's probably not a Virtual Machine you're looking for ^^
Click to expand...
Click to collapse
Well, I saw people that bricked by using DSU with locked bootloader, perhaps they fixed it with some update.
daniml3 said:
Well, I saw people that bricked by using DSU with locked bootloader, perhaps they fixed it with some update.
Click to expand...
Click to collapse
Well I assumed it was a way to flash myself when I got curious but I wasn't able to apply the virtual one, tried several times as well after.
That's all I ask for, remove my Gapps xDD but no
So ye if someone knows how to apply it I'll be interested ^^