How to #%^&* up yr Streak all by yourself ! - Streak 5 General

Found this over at the HD2 forum but it's relevant here!
Here are the top ways to screw up your Streak. If you are a non techie, pls read this!
1. Installing apps/apk's that are not meant for your Streak. This i think is the most common issue. Check the thread on apps list to ensure its safe. When in doubt, read the info or Check with others
2. Playing around with Rom. (installing 2.1 if you don't have a clue what you're doing) If you don't know how then don't do it. If you are game to test out new rom, read the step by step instruction CAREFULLY, if in doubt still DON'T do it.
3. Rooting. Falshing a boot.img This is highly risky if you don't know what it changes
When any of the above happens and nothing seems to work right, the most likely thing to do is do a hard reset.
The good news is after hard reset your phone might work again!

this is kinda redundant info since we are very lucky with the streak as right now there is no way to permanently damage your streak. unlike other devices which totally brick when a flash goes wrong.

Only number 3 has any chance of screwing up your streak, and even so, it would be a very easy fix.

Related

Questions about Flashing ROMS

First off, sorry if this post is in the wrong section. I thought this was the best place for it.
So, I am about to get a Cingular 8125, aka HTC Wizard or whatever.
Now, before I start the flashing roms deal, I wanna ask a few questions.
Before that let me tell you that I have a lot of experience with Windows Mobile 5 on a Cingular 2125. I've had that for about 2 years, until a water incident. Luckily I can get a 8125 because of my 2 year contract. Also, I'm not computer literate. I'm actually quite intelligent when it comes to computer type questions. This might not affect my knowledge with ROMS, but computer terms won't be hard for me to understand.
Okay, this is coming in the mail tomorrow afternoon. My questions are:
1. Can I ruin a warranty by flashing a rom?
2. What does "brick" a device actually mean. I know it means ruin it, but do you mean cause it to become unbootable?
I had a few questions but they slipped my mind. I'll post more questions if I can think of more.
Thanks for the support!
The term brick is used to describe a pda that is entirely unusable. A bricked wizard refers to a wizard that is unable to enter bootloader mode, and hence unable to be flashed with anymore roms.
Flashing roms is generally considered a void of warranty. It is often a good idea to flash back your original idea prior to submitting your device for warranty claims.
stuff said:
1. Can I ruin a warranty by flashing a rom?
Click to expand...
Click to collapse
CID Unlocking and flashing a custom rom voids the warranty. Period. But, they have to look to see that you've done this for them to hold that against you. So if something happens and you need to do a warranty replacement, then flash it back to an official rom (hopefully whatever happens doesn't render it unflashable). There are some that won't flash for this reason (or use the thread on how to flash without CID Unlocking that the G4's use. But I've heard some G3's have been bricked by this process).
2. What does "brick" a device actually mean. I know it means ruin it, but do you mean cause it to become unbootable?
Click to expand...
Click to collapse
A Brick is a term used to describe how useful the phone is after something went wrong and the IPL/SPL (like a PC's BIOS) has been hosed so its no longer bootable. Some have raised their phones from the dead (brick state) but using a process to flash rom the SD card (read the wiki as it has a pointer to how this can be done) or via JTAG (I only know of the process, not how or where to do it, but it involves opening the phone and soldering wires as I understand it).
Understand though that a lot of people here throw around the term "Brick" to describe when the phone just doesn't boot normally. IMO that is not a brick as the phone is "easily" recoverable.
So basically the only way I can "brick" the phone is by doing something completely wrong?
The first thing you should do is determine if your phone is a G3 or G4. You use different techniques with each one. Then read and ensure you fully understand the unlocking/burning directions for your particular model (G3 or G4). Also ensure you accomplish each and every step, don't skip anything.
calouro said:
The first thing you should do is determine if your phone is a G3 or G4. You use different techniques with each one. Then read and ensure you fully understand the unlocking/burning directions for your particular model (G3 or G4). Also ensure you accomplish each and every step, don't skip anything.
Click to expand...
Click to collapse
Will do. I'm hoping it a G3, that way I can have an easier experience and people can help me out easier.

What now?

First of all I just want to say WOW what an insightful and creative community you guys got going on around here. A lot of smart people on these boards. Thanks for the resources you guys provide to make having a cell phone into a hobby.
I have just successfully rooted my phone after hours of deduction and have flashed RC33 and a radio ending with 1.1. I've spent about 4 hours getting to this point and still feel behind the game. What motivated me to do this was the Official Hero Rom in the Android Development Thread and that is my ultimate goal insofar.
However, now that I've done this I don't want to take any unnecessary risks. I've used the dandy search feature and done hours of research as well as lurk on here since the launch of the G1 when I picked up the phone on launch day. I know about all of the informative links and they're great and I've reviewed them thoroughly but am still fuzzy on a few things.
I've read that there are different types of SPL's some brick and some don't. Please correct me if I'm wrong but my understanding of an SPL is that it is basically the update.zip file in my SD card. Currently that is a build of RC33 in my card along with recovery.img. For some reason I feel that this is not all as far as an SPL is concerned. If someone can concisely clarify this for me that would be great.
Also before I jump on Hero, what is a good cupcake ROM around here that is stable and not lacking many features that can easily be blinged out with one of the awesome themes you've got floating around here. I'm open to all enthusiastic suggestions. What tips do you guys have for me to move up to one of those?
I have not even begun to delve into App2SD or Nandroid but am getting a clearer image as to what they are and how they function. Any helpful tidbits on the two subjects would also be greatly appreciated, however they are not my main concern immediately.
Again thanks guys I've got work in about three hours now lol so I'm going to get some shut eye however I'll be back tomorrow. Soon, I hope to contribute to what you guys have got going on.
Unfortunately your hours of deduction did not lead you to this thread. Which has a link to this thread. Which has definitions, two I am posting here:
Bootloader – the SPL and IPL of a flash based device. See jashu’s description here.
SPL (Secondary Program Loader) - You get to the SPL by holding the camera button while powering on your phone. This is where you flash NBH images. See bootloader above.
Click to expand...
Click to collapse
Which links you to a greater explanation of what the SPL is.
Personally, I don't think the Hero builds compare with Cyanogen's Scary Experimental builds. I believe you sacrafice a lot of speed to gain very little (if any) functionality. Don't let the misnomer of "Scary Experimental" throw you off. His latest 3.5.3 blows everything else away. It's within a build or two of being declared stable. And most of the tiny little issues with 3.5.3 can usually be fixed with instructions being posted in that thread.
Moving over to Cyanogen's 3.5.3 is braindead simple too. Don't rush, follow the recommended upgrade path, and you'll be set. It does all the work for you, and it doesn't require the sometimes dreaded new SPL (which, BTW, is not nearly as risky as some will lead you to believe ... you just have to properly follow the required steps). Still, will this being your first attempt at any of this, you'll find it much less taxing on your nerves by sticking with a more straightforward upgrade. Cyanogen's is a great way to get your feet wet. And in the end, you'll end up with a blazing fast phone with all the bells and whistles too. Your phone will impress the moment it first boots. There are themes available now, and more will be coming once it hits stable. Apps2SD are automatically done for you if you have your sdcard formatted correctly. There are a myraid of ways to get the correct partitions on the sdcard, so do that before anything else. It will increase your chances of making this successful on the first attempt. Remember that a wipe is not necessarily a bad thing, it's usually that a failure to wipe is what caused your problem in the first place. Wipe if it's recommended. Read the comments to determine when it required, when it's just a recommendation, or when it's not necessary.
Be methodic. Since this is your 1st attempt at this, you'll be doing yourself a huge favor if you grab everything you need all at once. Don't try to take any shortcuts, follow the steps or instructions to the t. Make sure you have the latest radio installed (and the new SPL should you pick a build that requires it). Although they usually list the latest builds in the 1st post of a particular topic, occasionally they will release in intermediate fix within the thread itself. Check the last few 10 or so pages of comments for your build of choice to see what build is recommended at the time. Usually, you'll want to grab the latest build, but that's not always the case. Bleeding edge is not always best (althought with C's Scary Experimental, I've eagerly awaited each and every update because it's only gotten better each time).
Since you've done your research, go back and outline the entire upgrade path. Write it down for reference. Make sure your Windows driver are up-to-date, have the latest ADB installed on your computer (it makes things much easier if you use ADB if possible), don't do anything until you can devote a couple of uninterrupted hours to the upgrade process, and I cannot emphasize enough to WIPE as necessary. Hell, don't install any programs or fiddle with any settings. WIPE each step along the way until you get the final build installed. If something doesn't seem right any step along the way, don't proceed to the next step. WIPE again and re-flash. See if that fixes your problem. If it does, the proceed. If it doesn't, see if it's an issue that fixed with the next build you'll be flashing. If so, proceed. If not, look for another solution. Proceeding at that point _might_ be okay, just be aware that you might get yourself into a situation that requires re-rooting your phone.
Make sure that before you do anything else that you have one of the modified recovery images flashed to your phone. They're modified for a good reason.
If things go bad, don't panic and start posting that you've "bricked" your phone. Chances are you haven't. Very few phones get "bricked" to a point you can't fix it yourself. When people around here see the term "bricked" as a subject in a post's topic, it's a red flag that becomes a red herring for you. You may get into a boot loop or something, but it's usually fixable with a WIPE and an update.
Also, keep DREAIMG.img in the root of your sdcard at all times. Don't move it, don't delete it, don't rename it. It can, and will, save your ass if any of this hits the crapper. Carry it with you at all times. If you have DREAIMG in the root directory, you'll always be able to get your phone back to an operating condition, wherever you are, whenever you might need it, without the need for a computer. Yes, it would be starting all over again, but it would give your phone basic functionality if all goes to hell and you're not near a computer or don't have a USB cable or something.
None of this requires a PH.D. It's actually quiet simple. Most people that run into problems have simply missed or skipped a step, or failed to wipe as required. Knowing recovery proceeds in advance will be helpful, but even that is pretty straightforward and easy to follow. I've done all these flashings, re-flashings, recoveries, etc., so much that I --think-- I have the terminal commands etched in my memory. And I do. But I still refer to the on-screen steps to make 100% sure I'm typing things correct. I hit enter only after I'm confident I didn't type a 0 when it should be O (hehe). I look at the screens during the whole process for indications of success or failure. And I make sure that I am not distracted by anything when I upgrade. Lock yourself in a room by yourself after you've emptied your bladder. If you do get interrupted or have to take a bathroom break, write down the next step. Don't assume you'll remember. And don't even think of making or taking phone calls until you've finished this whole thing.
Read in advance.
Search as necessary.
Ask, in the appropriate forum and thread, when all else fails.
You'll do fine.
Good luck.

[Q] Brand new to rooting - questions....

Hey guys... I am brand new to all of this... just got my samsung vibrant a couple of months ago and love it. I have since always wanted to root my phone, but am scared of doing so because I don't want to void my manufacturer's warranty on it (and i'm paying for an extended warranty). I was reading through the "guide - tips - tricks" post and found a LOT of good information. But it did not really answer my questions due to me being so new, so anyway, here they are:
1. Do I need to create a back-up of my system the way it is before I root? if so, how do i do it (in beginner's language w/ step by step instructions pls). I saw where I can down load the "ROM Manager App." But I don't even understand what "Flashing" the Rom means?
2. I didn't understand the post about returning your system back to a "factory OS" the way it was when you received your phone... (http://forum.xda-developers.com/showthread.php?t=728471 )In this post he explains supposedly how to do it, but I don't understand entering that stuff in a "terminal" on your computer... could someone explain in noob terms w/ step by step instructions?
Just to make sure... in theory, I can make a back up of my system before I root. Then I can root my phone. But if I ever want to "unroot" it, then I would have to follow the instructions in the link above, and then afterwards do a recovery of my nandroid backup to put me back to where I originally was? thanks guys
Rooting your phone will change nothing (meaning you lose nothing).
So, after you root, simply download Rom Manager, open it, click on flash recovery, then reboot into recovery (at this point you can make a backup of your phone).
Once you have root, you can also use titanium backup (in the market also) to backup all of your apps.
flash = install a rom *you do this in recovery, see above*
If you know nothing about this the best advice is to read the very first thread in this section. It walks you step by step from "hey I want to root" to "I'm rooted, Now what?" to "Hey I F'd up, can I fix this" and so on. And on the "Hey I f'd up" note apparently the Vibrant likes to brick, meaning it won't turn on and you'll think you broke it, so you need to be familiar with ODIN which you'll find out more about in the three threads I refer to. Also the first two threads in the Development section are also must reads. All of the answers are here. A lot of people here will be very helpful in giving guidance or pointing you to the answer your looking for but there are quite a few that will flame you for not searching.
You'll be much happier and more comfortable after reading these three threads. Good Luck.
Answer to question 1 can be found here. http://forum.xda-developers.com/showpost.php?p=7324731&postcount=1
Answer to question 2 can be found here. The terminal you speak of is ODIN. Kind of a fail safe if you will. http://forum.xda-developers.com/showthread.php?t=734475
A "I need to send this back for warranty repairs" backup isn't critical since you can just load up Odin and flash it back to stock with that. No need for you to be hyper critical on that.
With this phone, pretty much anything you can mess up can be fixed with Odin (short of flashing things that aren't meant for this phone).
While I wouldn't volunteer to be the first to flash an image, I wouldn't be too scared of it either.
Rooting your phone will add a few files (superuser, busybox) and otherwise leave your system intact. If something breaks later & you need to sent it back to TMO/Samsung, you'd just Odin it back to stock and give them a "blank slate" which is actually something you'd want to do anyways (you don't want them having access to your gmail for example...when I send a laptop back for repairs, I always image it back to stock as well).
I would suggest you read through the Vibrant Bible and just poke around. When you see something that shows/tells you how to do things like flash, follow along (load up the software and do as much as you can without actually doing anything [if that makes any sense]).
Never EVER flash anything that wasn't meant for your phone (a few people bricked their vibrants by accidentally flashing the SPLs from their G1s...how they make that mistake I don't know, but it's happened). Be careful, follow directions & you'll be good to go.
There are youtube videos showing how to use Odin and get back to stock (I believe the bible has links) and there are probably also youtube videos showing how to do other things as well.
For root, all you have to do is download "RyanZA's OCLF 2.0" from the market and click the root button. Follow its directions & you are good to go.
For many of us, that's not good enough. You'll want to then install ROM Manager and have it download the new Recovery.
From there, the world is open, find a ROM and flash away! I'm partial to Bionix, but have recently started to like the Axura froyo ROM as well.

[Q] Having second thoughts

To start off with I have had my phone rooted since my g1 in 2009. I did not hesitate to root my mytouch earlier this month and it was successful. Unfortunately, my phone would no longer boot (not turn on at all) after a week of being rooted. I am not sure if rooting caused the error but now I am afraid to root my replacement. I wanted to at least flash my backup but I am afraid to even root for that. Also I should add that I root to flash roms not because I think it's "cool". Can anyone give me advice on if I should root again?
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
tenbeau said:
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
Click to expand...
Click to collapse
Yeah, I had flashed the hd port after using the z port and that's when the issues started. I think I will root again and just try to be more careful even though i am pretty sure I followed all instructions.m
Sounds like to me it was just timing between phone hardware and your flashing. Unless you are screwing around with with the ROMs prior to flashing without knowing what your doing you should have no issues. If it was ROM related you would see these boards all lit up with people having the same issues...and you simply dont see that.

Question I've tried so hard and got so far.

Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?

Categories

Resources