Develop Bugs

Short success story after all - useful reading esp. before flasing your ROM

Motto: There is always hope.
Let me share with you, other xda forum members, the following story - I think it might be useful for some of those who already got problems with the upgrade procedures, and especially for those who just now contemplate to try their luck and launch the upgrade (to whatever WM version or AKU).
After successfully going through the reflashing procedure several times on my O2 XDA Exec precciousssss gadget (flashing Helmi_c 1.1 Crossbow, then JWright 06 and later JWright 08) I was confident enough (overconfident, perhaps?) to go on and reflash also my wife's i-Mate Jasjar (there were some issues all the same and I was recently thinking of restoring the factory defaults through the hard-reset).
JWright's ROM offers a very simple, almost luxurious, way to upgrade - basically the same as any of the official ROMs - just click the .exe file and pray. And there is the hitch - it says somewhere you need a 1.01 version of the Bootloader but I didn't know how to find out the version of the bootloader present on the unit in question without launching the bootloader itself through the "bulb - switch-on - reset" combination; and I admit (yes, the effect of over confidentiality, indeed) I was somehow too lazy to go and check (by the way, is there a way to find out what bootloader version you have other than the way mentioned above?). Somehow, perhaps, I thought the upgrade would indicate the bootloader mismatch prior to the system reflashing or what. And after all, the JasJar unit was purchased at almost the same time as my XDA Exec and there I knew I got a 2.0.1 bootloader version, so why to bother - silly me!
OK, here we go.
Flashing > "success" > unit "bricked" (no LED lights, USB unit not recognized by the PC, no signs of life of the poor thing not able to do anything but to accuse me by its doomy pathetic black screen of mishandling, asking me at the same time WHY have you done THIS to ME?) > moment of unpleasant, uneasy feelings comparable only to those created by a dozen of hamsters running their wheels in your stomach.
Now the good part of the novel:
Even before flashing my Exec for the first time, I diligently spent (a lot of) time reading all the relevant forum posts, downloaded emergency tools and was therefore prepared for the fact, that something might go terribly wrong.
Million thanks to all those who contributed to this forum sharing your knowledge and know-how, because based on your shared experience I was able to discover myself at the moment of utmost horror what the problem was (yes, in my case it was the bootloader issue - the JasJar got some 0.6 version of it - ever heard of it? I was considering the mtty Midget_1990's or the Mamaich's solution first, but then I recognized the boatloader's trickery and the right way to solve the crisis was in my case just to upgrade the bootloader through the known and somewhere here at this forum very well described ROMUpgradeUt bootloader procedure; to make the long story short, without the appropriate version of bootloader the unit will not boot, that's it).
Now the JasJar is fully recovered, happily running the WM6 Crosbow ROM, exactly as its O2 Xda Exec brother.
Lesson learnt
I strongly suggest that everybody does their homework in reading all relevant forum threads before venturing anywhere futher. It is only natural that after bricking the 1000 USD toy, most people will have problems to concentrate on anything of a substance and chances are, that instead of fixing the problem, you may mess everything up even more and end up in a deeper and hotter circle of hell without any return ticket.
And it needn't be like this, it is possible to avoid it!
I don't want to give anybody any false feeling of security and comfort due to my particular happy-end case. Every unit is perhaps slightly different, conditions are different (cable, PC OS...) etc, but most of the problems seem to have their solutions and by diligent reading of the relevant Xda forum posts, the chances of getting over the troubles through the shared know-how are high.
So stay cool and happy flashing.

Very wisely said Bonasa. Appreciate all your experience undergone. In fact this is the wise way to upgrade by reading more and keeping tools handy.

nice one Bonasa. I spent almost half of 2006 reading stuffs here in xda before I had the guts to use any of the ROMS here 2 weeks back. To those attempting to flash the first time, Bonasa said it all

Excellent post Bonasa. This gives a lot of information to first time upgraders. Your experience will surely help others in similar situation.

ok now im scared... i just bought my i-mate jamin yesterday and i really want to upgrade my wm5 to wm6... its just an oppsession to always have the newest things i guess... but im scared to screw up at some point and make my new device life-less
did anyone try to upgrade his i-mate JAMin with Helmi_c 1.1 Crossbow before ? btw what's crossbow ? :S
and how can i avoid this " bootloader " issue discussed by Bonsaa?
plz help...

Last week I made my first upgrade. I took the chance with the new Jwrightmcps ROM.
As you said, it's VERY important, I would say MANDATORY to read most of the threads in the forum.
My forum Join Date is 30-10-2006. Only after 3 months I made the first upgrade.
It's very nice to get a new ROM but we must be patience before doing it.
Last point:Before the upgrade I also got the "unbrick" tools , just in case...
And I had a stupid problem: stuck on bootloader: REASON, I didn't use the original cable during the first upgrade attempt.
Read before you try anything!
Cheers

Wild speculation

I don't have the experience to know if this is possible, which is why I ask because I'm curious. I post here because I want devs to see it, and think "that could work" or "idiot"
As we know the defy bootloader will probably never be unlocked, now I was thinking would it not be possible to somehow isolate the bootloader from a rom, and run some kind of virtual one in a seperate partition to run a fully custom kernel? It's probably crazy but I'm dying to know what people think, don't be too hard on me I have no coding experience :/ however all opinions are welcome I think anything is possible
Sent from the real world by hacking into the matrix

I don't want that this will become another dead Bootloader-Hacking-Thread but I want to give you an answer with the facts:
1) There currently is no known way to execute code before booting the kernel because everything is well protected though signing code.
2) The only way to boot a kernel after kernel-boot are tools like kexec or 2ndboot. But a phone's RIL is a heavy stone on that way because it's not that easy to reinitialize this part of hardware and without RIL a phone is useless. The main-developers canceled this project due to this reason.
Other "non-phone"-devices with locked bootloader (like Sony's google-tv) are using this method without problems.
3) You can use kexec/2ndboot to load a full bootloader instead of an kernel only, too. But because we don't have the source we would have to reverse engineer it to disable the signature check of the kernel otherwise you would load another useless protected bootloader This was also an project but I don't think it's still alive...
Additional note: You can't directly flash a modified bootloader because our chipset has built-in OMAP3-security features. This means the CPU will only boot signed Code from NAND.
You can find many helpful information about this topic on this page:
http://and-developers.com/partitions:cdt#cdt_table_of_droid_x

Thanks that clarifies things quite a bit, however I mean loading not just a second kernel but a WHOLE bootloader that would handle the phones entire functions independently, or is it completely hardwired so its impossible for something to override it? (Sorry if you have already answered in the above). Another thing, has noone tried to compile custom fixed sbf? Maybe the bootloader could be replaced that way? In software almost anything done can be undone in some way, although perhaps this is the rare case where it isn't
Sent from the real world by hacking into the matrix

I edited my post to have everything at one place.
I hope this answers your questions.

The bootloader is like the bios in a pc (actually is part of the bios), it's what initializes the device and loads the rest of the code. to load it again or another one you had to reinitialize the device. the issue with the RIL is that when reset or restarted it "panics" and resets the whole device (I think, read it somewhere).
also the second unlocked bootloader that you want to load does not exist anyway.
it's better to just help the developers with bug reports and testing than daydream.
sorry mate!

m11kkaa said:
I edited my post to have everything at one place.
I hope this answers your questions.
Click to expand...
Click to collapse
So its all been tried before, damn! XD at least the devs here have done a fine job of making good roms even with this limitation, guess I will do my research before I buy my next phone as I love playing with roms, the more custom, the better
Sent from the real world by hacking into the matrix

Is root possible for SAMSUNG-SM-N910A on 5.1.1 build number LMY47X.N910AUCU2DOI3 ?

I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.

from where have you downloaded N910AUCU2DOI3

Latest update from AT&T through system update.

At this time there is none. There likely will never be permanent root for this device, either. Best hope is for a future update of KingRoot to come that gives a very buggy temp-root.

naverone said:
I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.
Click to expand...
Click to collapse
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
teddyherrera1 said:
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
forgot to tell you the two U.S. carriers that put locks on their bootloaders is AT&T and VERIZON so i wouldnt recommend root unless you unlock bootloader or else your phone will continueously stay in boot mode without letting you exit. that i believe is a bootloop good luck

teddyherrera1 said:
Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK.
Click to expand...
Click to collapse
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
teddyherrera1 said:
Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it.
Click to expand...
Click to collapse
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
teddyherrera1 said:
For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.

How I root Samsung Galaxy note 4 SM n910a 4.4.4

spexwood said:
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.
Click to expand...
Click to collapse
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.

Spooters said:
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.
Click to expand...
Click to collapse
1) That post was made back in 2016. That was over 2 years ago!!! Why did you necro such an old thread? The last post made here was Dec 5, 2016.
2) I no longer have the n910a. Got rid of it a long time ago
3) I do not, nor never have worked for ATT nor am affiliated with them in any way.
4) When I used the word "our" I was referring to the fact that I too owned the n910a. So "our phone" obviously meant "my n910a and everyone else's" and same for the "our bootloader"
5) At the time of my post, root was not available for rhe n910a AT ALL. (If I recall, a temporary root eventually became available though, but it reset everytime you restarted your phone). On a daily basis, people were asking whether root was available or not and people were getting sick of answering the same question over and over again when the answer fould easily be found through a simple search here on XDA.
There were also scams going on at the time BECAUSE this was such a popular topic. Websites claimed to give walkthroughs on how to root your n910a, but all they really did was brick your phone. Kingroot was one of them.

You people writing these rooting and unlocking guides are completely insane.

I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.

notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app

gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.

notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.

douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.

Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.

Question Getting to know my Biloba - fixing it - nonGoogle

Dear tech friends
I happen to own a Biloba Redmi Note 8, and I understand now that it isn't the best phone for DIY. But I want to make the best of it as selling it will mean loss of money and overall I am very pleased with the thing. Or maybe 'was'? I hope I did not kill it.
The situation:
- it is stuck in a kind of startup loop that restarts endlesly. I need to put the phone in fastboot to give it some rest. I believe I managed to shut it down yesterday, but I do not remember how.
- this happened after I installed a (wrong?) recovery rom into the boot sector - this was before I realized how particular this Biloba version is.
- I want to fix it and put a google-less rom, perferably open source/GSI but if not possible official China Rom could be an alternative as it doesnt have Google.
My question to you is foremost: where can I obtain the knowledge to fix this myself? Ebooks, tutorials, Xiaomi service manuals? Mind you: it is BILOBA.
Also I havent found any decent MiFlash program. They all seem buggy as hell. Doesn't Xiaomi offer official tools for this?
Why is smartphone administration seemingly shrouded in mystery? Companies do not want us to amdinister our phones ourselves? PC technicalities are so much more accesible it seems?
Thanks people!
pyrkaios

same here

I guess the best places are the threads on xda on devices that have more active modders.
I usually use 'Google', and mostly keep in mind a way to return to previous conditions.
Keeping a copy of original firmware ready helps there.
Also, I tend to flash with fastboot whenever possible.
Only reason not to is when I must flash when in BROM.