Related
I have been wondering if I should attempt to root my phone or not. With the new rumor claiming that Google's newest updates (donut eclair flan ect..) will not be distributed out to the G1 users due to hardware issues. It seems if this rumor turned to be true the only way to get the new said updates will be to root my phone. My worry is that i will end up bricking my phone. Now to the Question.
If by some chance i end up bricking my phone is there any way to unbrick it or would i be SOL because rooting voids warranty?
I advise you to read the ultimate noobs guide up and down http://forum.xda-developers.com/showthread.php?t=550710&highlight=ultimate+noob
After you have read that then goto youtube and watch the 3 part series at this link.http://www.youtube.com/watch?v=GgJ2VtSqtJY&feature=channel_page
If you follow these guides, you shouldn't have any problems.
Thanks for the links. The n00b guide i knew about. I was planning on using that when the time came for me to root my phone. I just wanted to know about bricking just as a fail safe. I have read that once a G1 is bricked there is no going back but i have also read with the new updates there is a way to restore a bricked phone. Just wanted some clarity.
A real brick is just that, a paperweight, no coming back. The real only way to brick at this point is the danger spl needed for a hero rom, other than that any boot loops or jam ups as long as you can get into recovery or the bootloader you can be saved with a little bit of reading, and don't worry we will get the updates just our xda versions of them
Now I'll begin by stating that I know very little about flashing and as much as the great people have tried to explain things. Its all a bit cryptic! especically when you see/read updates here and there. I did try to use the tutorial at the start of this thread (seemed easy enough) but hit a wall when I couldn't work out what I was supported to run RUU? Anyway I did find what I'd have to say is the perfect (read easiest) way to do these flashes. Its all based on the stuff the very smart people here have put together but is presented in a more 'user friendly' manner.
Visit: http://thewingster.com/roms.aspx
Choose your ROM (Wing or Touch Pro), I have a Wing and went with the following which allows you to choose what you want. I found choosing everything wasn't a good choice! So I went with the base, then I can install what extras I need afterwards.
http://thewingster.com/choic3s_1.aspx
Then follow the very easy instructions here:
http://thewingster.com/howtoflashnbhuspl.aspx
Note you dont have to worry about doing HardSPL and the like (it must do that as part of the manger software - and you can run it multiple times!! I did as I write I'm on my 3rd ROM!!)
Then you're good to go! I wish I'd found this and 'understood' how easy this was. Kudos to the wingster for doing this, just wish he'd make it even more obvious how easy it is to do! (remember we're all paranoid about bricking our phones!)
Well I hope this helps those who like me was clueless - I might still be clueless but I'm now running WinMob 6.5!
Oh I should also point out that the requirement for SPL 4.XXX still applies (see first post for how to work this out) and I have no affliliation with wingster - just greatful!!
Flashing custom ROMs without first being HardSPL is not advisable or safe for your device. Certain ROMs do not require it, but it is highly recommended as it virtually brick-proofs your phone, and it is fully reversible if you ever need to go back to shipped condition.
Also, this is not posted in the correct forum. This is the Herald Mobile 6 forum, not 6.5, and should be posted in the Herald forum.
They're right!
They're right; the Wingster website is fantastic and I've downloaded just about everything that is on the site and backed it up on a partition. Just do exactly what these instructions tell you to do and once your phone is HardSPL; it literally takes an act of God to brick your phone.
Ok first off I have tried searching all day this both here and and on Google, and all I see is "soft brick" or "brick!!!1!!" threads that have access to the bootloader. So either I am being obtuse or it is buried deep in an obscure thread.
Here is my situation, I unrooted my phone by doing the following: I had used DREAIMG.nbh to return my phone to RC29, flashed the cupcake update, and waited for the donut OTA because the .zip would not successfully flash.
All of that was done and everything was running great for a couple of days and I decided that I wanted to go back to rooted.
Well I was using clockworkmod recovery before and I had made a nandroid back-up before unrooting. I figured that would cut the work in half for when I went back to rooted. I didn't know that AndRoot was available for G1 1.6 so I did it the old fashioned way and reflashed the RC29 DREAIMG.nbh. I then regain root via the original 'telnetd' method and proceeded to flash cloworkmod recovery via Telnet. In the nandroid backup that I made I was running Super F test3 so I know that I needed the danger SPL. This is where everything fell apart, I placed the Danger SPL zip on my sdcard and rebooted to check that the recovery had indeed flashed successfully (it did). Seeing that it was working, I then selected to flash any zip update and selected the Danger SPL. It ran and said the operation completed successfully. I then home & backed to reboot and now I am stuck with just the G1 splash screen.
1) Home & Power does not work
2) Camera & Power does not work
3) Trackball & Power does work to get in blue LED mode. Don't know if that helps just laying it out there.
4) I did not flash a radio, I know the dangers there. This occurred immediately after flashing the Danger SPL via clockworkmod recovery.
To summarize: recovery & bootloader button combos don't work, blue LED mode does, phone does power on but I only get the G1 splash screen for all button combos aside from blue LED mode.
Any help is appreciated, an thank you in advance.
I'm going to call this a brick unless you can get JTAG.
When flashing the danger spl, just follow all the instructions including re-flashing any radio.
UberMario said:
I'm going to call this a brick unless you can get JTAG.
When flashing the danger spl, just follow all the instructions including re-flashing any radio.
Click to expand...
Click to collapse
I didn't need to flash a radio yet, I was just trying to get back to the Danger SPL so that I could restore via nandroid and then I was going to flash the 2.22.23.02 radio because: 1) it worked well for me, and 2) it is Danger SPL safe
I think you mixed things: the correct radio is a precondition to flashing DangerSPL. Flashing RC29 you most likely reverted your radio to a 1.x-version.
In addition to that, there is no need to flash DangerSPL. Go with Firerat's custom mtd method and 1.33.2003 and you are fine.
Sent from my Htcclay's Superfly G1 BTX using XDA App
Roadmasta01 said:
I was running Super F test3 so I know that I needed the danger SPL. This is where everything fell apart, I placed the Danger SPL zip on my sdcard and rebooted to check that the recovery had indeed flashed successfully (it did). Seeing that it was working, I then selected to flash any zip update and selected the Danger SPL. It ran and said the operation completed successfully. I then home & backed to reboot and now I am stuck with just the G1 splash screen.
Click to expand...
Click to collapse
YOU DO NOT NEED DEATHSPL FOR ANYTHING!!!!
It has ZERO benefit and introduces the possibility that you may do what you did. You know, there is a REASON why we developed a method of repartitioning the thing!
You're BRICKED.
lbcoder said:
YOU DO NOT NEED DEATHSPL FOR ANYTHING!!!!
It has ZERO benefit and introduces the possibility that you may do what you did. You know, there is a REASON why we developed a method of repartitioning the thing!
You're BRICKED.
Click to expand...
Click to collapse
Really? Yelling at me is going to help or fix my situation? I was simply working off of the limited knowledge that I have. I had not gotten into MTD partitioning. I felt that that was a little above my head and there for the working knowledge that I had was that I needed the Danger SPL to resize the partitions to enable the flashing of ROMs that need a larger /system partition.
And just for back-up here is quote from Cyanogen's thread for CyanogenMod 6
cyanogen said:
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
It's important to know that the "DangerSPL" (or DeathSPL or Haykuro's SPL or whatever you prefer) is a prerequisite for Dream/G1 users. Magic (MT3G etc) users do *not* need to do this. Ciwrl has written a guide to installing this bootloader. Flashing this bootloader under the wrong conditions can actually brick your device, so pay attention to the guide. CM releases have always avoided this requirement, but the new bootloader frees up enough space so that no crazy hacks are required for a fully functional system, and it's easier to keep in sync with the N1/Droid releases.
Click to expand...
Click to collapse
All I was asking for is a little help, I came into this post think that I was hard bricked, I was just hoping against hope that I wasn't. I am not, and neither are a lot of people that modify their G1s, an expert at this. I am one of the original G1 preorders; This is my first and only G1, and this is the first time that I have bricked my phone. That fact alone should tell you that I have tried my best to read as much as I can to understand something before I try it. I simply became complacent in my working knowledge, which led to this. I am sorry that I was ignorant of, or apprehensive to try some new developments in partitioning, rendering the Danger SPL irrelevant. Please don't needlessly yell at people for no reason. At least I was able to concisely describe my situation and you all didn't have to play 20 questions to get the real situation out of me. I now know that the mistake that I made was forgetting that the DREAIMG.nbh file restores the radio to a pre 2.xx.xx.xx radio and seeing as how I didn't flash a compatible radio before flashing the Danger SPL, I am now hard bricked. Now that my rant is now over I will again say Thank you again to UberMario, and AndDiSa for their help.
I am now going to investigate the cost effectiveness of JTAG versus a donor motherboard.
Roadmasta01 said:
Really? Yelling at me is going to help or fix my situation? I was simply working off of the limited knowledge that I have. I had not gotten into MTD partitioning. I felt that that was a little above my head and there for the working knowledge that I had was that I needed the Danger SPL to resize the partitions to enable the flashing of ROMs that need a larger /system partition.
And just for back-up here is quote from Cyanogen's thread for CyanogenMod 6
All I was asking for is a little help, I came into this post think that I was hard bricked, I was just hoping against hope that I wasn't. I am not, and neither are a lot of people that modify their G1s, an expert at this. I am one of the original G1 preorders; This is my first and only G1, and this is the first time that I have bricked my phone. That fact alone should tell you that I have tried my best to read as much as I can to understand something before I try it. I simply became complacent in my working knowledge, which led to this. I am sorry that I was ignorant of, or apprehensive to try some new developments in partitioning, rendering the Danger SPL irrelevant. Please don't needlessly yell at people for no reason. At least I was able to concisely describe my situation and you all didn't have to play 20 questions to get the real situation out of me. I now know that the mistake that I made was forgetting that the DREAIMG.nbh file restores the radio to a pre 2.xx.xx.xx radio and seeing as how I didn't flash a compatible radio before flashing the Danger SPL, I am now hard bricked. Now that my rant is now over I will again say Thank you again to UberMario, and AndDiSa for their help.
I am now going to investigate the cost effectiveness of JTAG versus a donor motherboard.
Click to expand...
Click to collapse
When you do something RETARDED and WITHOUT THINKING, you DESERVE TO BE YELLED AT.
You asked for it, YOU GOT IT!
And you DESERVE it.
lbcoder said:
When you do something RETARDED and WITHOUT THINKING, you DESERVE TO BE YELLED AT.
You asked for it, YOU GOT IT!
And you DESERVE it.
Click to expand...
Click to collapse
I actually was thinking when I flashed it, I obviously just forgot about the radio reversion. Also, by your logic, since you are being a complete and total JACKA$$; Don't you deserve a nice left hook to the jaw?
Roadmasta01 said:
I actually was thinking when I flashed it, I obviously just forgot about the radio reversion. Also, by your logic, since you are being a complete and total JACKA$$; Don't you serve a nice left hook the jaw?
Click to expand...
Click to collapse
Try that and you could find yourself with a broken neck.
And IF YOU HAD A BRAIN to begin with, you would realize that REPARTITIONING THE SAFE WAY USING KERNEL ARGUMENTS is designed SPECIFICALLY to keep moron retard newbs like you from doing what YOU DID!!!!
I had not gotten into MTD partitioning. I felt that that was a little above my head
Click to expand...
Click to collapse
So... the easy and safe way is above your head, so you took the dangerous and difficult option instead? Sound intelligent to you?
lbcoder said:
Try that and you could find yourself with a broken neck.
Click to expand...
Click to collapse
You should really calm down, I didn't threaten you. I simply used your logic to state what you deserve.
lbcoder said:
And IF YOU HAD A BRAIN to begin with, you would realize that REPARTITIONING THE SAFE WAY USING KERNEL ARGUMENTS is designed SPECIFICALLY to keep moron retard newbs like you from doing what YOU DID!!!!
So... the easy and safe way is above your head, so you took the dangerous and difficult option instead? Sound intelligent to you?
Click to expand...
Click to collapse
I don't know enough about modding kernels to even know what kernel arguments are, so yes I feel that is a little above my head. I have been using the DangerSPL for quite a long time now and this is the first time that it has biten me in the a$$. Difficult? What is difficult about flashing file in a certain order? I have updated the radio a few times since having the DangerSPL. The first couple of times I had to reflash the HardSPL, flash the radio, and reflash the DangerSPL. The last time all I had to do was flash the 2.22.23.02 radio on top of the DangerSPL because it is supposed to be DangerSPL safe. So considering that I knew the dangers involved with it and it isn't difficult to put three files on my sdcard for all of maybe ten minutes, yes the DangerSPL path was an intelligent choice for me.
I've been doing a lot of reading regarding rooting the Nexus one and unlocking the bootloader etc. I wish not to unlock the bootloader at this stage (as you can't lock it again, and the fact that i'm gonna be playing around with my dad's phone and wouldnt want anything to happen to that)
Right now, the phone has stock 2.3.4 installed, which I believe needs to be downgraded to be rooted.
So I downloaded the FRG83 release.
Now is the following right/possible:
Flash the phone with FRG83 by going into the phone's recovery - so the phone is downgraded
Root the phone using the superoneclick method
Now the phone is rooted and I can flash it with any custom ROM eg, CyanogenMod 7 etc..?
Sorry if this has been covered earlier, however I tried my best to read as much as I could, however there were always a few more steps involved in the process which I thought could be left out
So would the above process be okay?
Thanks
You have to use the PASSIMG.ZIP method to downgrade.
I would just read the WIKI
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Read the wiki. You said you been doing a lot of reading but still do not know how to root/downgrade from 2.3.4. That makes no sense.
The steps are there for a reason.
You don't know what you're doing but come to conclusion that you can skip/leave out steps. That is flat out stupid.
Thanks
Thanks baseballfanz Yeah I've read the wiki and I was going to use the PASSIMG method, hence downloaded the FRG83 file, but somewhere else I had read that you had to flash it to froyo then back upto gingerbread :/ hence was a bit confused.
The problem is there are too many threads about it. And there are a few tiny differences in all.
So I guess I have to flash down to froyo and then use superoneclick.
And after that, I can just flash any ROM from the forum?
Alubundy2010, mate I did read it all and understood it. However I still had a few questions. If you didnt wanna help, it would've been best to keep your mouth shut.
Thanks
It is clear you did not and still don't understand it.
Yeah probably not, hence why I posted asking for help in the first place. Just spent an hour trying to do it, but stuck at froyo for now till I do an official OTA update tmrw morning and have a stock unrooted phone, cus I honestly don't have the balls to brick my dad's phone. So not rooting till I'm 100% sure of what I'm doing.
Thanks a lot for all the amazing the help.
Wiki clearly says:
"Gingerbread 2.3.4 can be rooted only when downgraded to 2.3.3 or to Froyo, using PASSIMG method, which will wipe the phone"
And the link is given - landing you on the same page, a bit upwards. The link contains EVERYTHING needed to downgrade.
Moreover, the following sentence points you to a VERY simple guide, which says: when you downgrade, you root. Without any additional steps. And from that point you do whatever you want.
The main guideline of XDA should say - "if you don't know what you're doing - stay away from rooting until you do". Obviously you don't, and you don't seem willing to learn by reading the proper guides, even when pointed to.
And just to make sure you got it: you can't root the latest OS version. Which means, if you downgrade and wait for the OTA to upgrade you back to the latest version, you'll finish (again) without the ability to root, and this time also without the ability to downgrade. Not quite smart, yes? If you want to avoid unlocking the bootloader, that is.
Now that the phone is running froyo you can root.
You should also have gotten the ota notification basically as soon as the phone finished booting.
Sent from my Nexus S using XDA App
I've read through
http://forum.xda-developers.com/showthread.php?t=939243
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
http://forum.xda-developers.com/showthread.php?t=636795
http://forum.xda-developers.com/showthread.php?t=705460
http://forum.xda-developers.com/showthread.php?t=1084978
think that's a fair few guides I've been through, and that's probably why I can't get it write cus I'm jumping from one page to another :|
Oh well thanks for the help guys, and I did actually do all the reading that was required.
Oh and I also rooted the phone when it was on Froyo through the manual superboot process.
Is "Copy partitions zip" still needed when prepping for roms with official firmware?
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
we still need it. which video doesn't have this step? pretty sure i did mention it in all the videos. if i did not , then my bad.
Hey man thanks so much for replying! I haven't actually seen it in any of the videos - unless I'm missing something incredibly obvious.
(for context - my ultimate goal is to flash LineageOS 15.1 and get root passing SafetyNet to the point where GPay works)
I started here to get the basics:
https://www.youtube.com/watch?v=bkmczD9tvEQ
This video starts right with flashing the stock firmware:
https://www.youtube.com/watch?v=2-Kcwjyk_Ls
This video I didn't understand at first, but eventually got that you're just explaining A/B slots, not necessarily giving a tutorial:
https://www.youtube.com/watch?v=zVwYxp30dps&t=119s
None of these have that specific zip being flashed.
So if I understand correctly the correct process after buying the phone would be...
1) Unlock bootloader
2) push needed zips to phone storage
3) fastboot into TWRP
4) flash copy-partitions-payton.zip
5) reboot into recovery
6) flash stock firmware (I'll be using PAYTON_FI_8.1.0_OPWS28.46-21-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
6) ...and basically follow the rest of your video to a T from there.
Hey I was wrong sorry - it's totally in the Android P video. So that was super helpful... and I just finished flashing everything successfully! I did not seem to have to flash the stock firmware at all - I simply flashed copy-partitions-payton.zip, did a factory reset, and moved right on to flashing LineageOS.
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
This is also missing from the official Lineage documentation, fyi:
https://wiki.lineageos.org/devices/payton/install
Thanks for your videos, they've been super helpful and so far no problems with my flash.
amirite said:
So does this mean that copy-partitions-payton.zip and flashing a copy of stock firmware accomplishes the same thing?
Click to expand...
Click to collapse
What do you mean by flashing a copy of stock firmware? Where is it asking you to flash stock firmware, the guide assumes you are on stock firmware. Also, if you have LOS already running dont bother about it too much. The original instructions explaining all this were in the LOS thread I created, which was transferred to Erfan once LOS was official. Now, the original instructions are no longer there. So, just forget about them and enjoy your custom rom :highfive:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
amirite said:
I surely am Everything is running perfectly, except for a couple of minor crashes of the settings app. No biggie. Thanks again for the reply, I'm sure I'm mis-reading a few things pretty badly, but this is helping.
When you use the flash_all.sh script in your videos (at 4:45 in the 2nd video), is that not flashing the stock firmware? Isn't that zip directly from Motorola and flash_all.sh flashes the entire phone back to stock?
I assumed that flashing the stock firmware was a way of putting the phone in a known-good state before continuing with you guide. But then you talk about how Motorola didn't populate the B slots. So I'm just not exactly clear on what the copy-partitions-payton.zip does. I did flash that, but I didn't have to use flash_all.sh at all.
Click to expand...
Click to collapse
What I understand is that Moto does not flash both slots by default, but flashing the flash-all does both slots with the stock firmware. If you are on the default stock setup, copy-partions will just copy your the Moto default to the other slot.
Got it. So basically the main goal with that first step is simply to populate the B slot which can be achieved by either method. Thanks guys, I just wanted to make sure I understood the full scope of what had to be done. Always an adventure catching up to the many months of hard work y'all do to get us here. Much appreciated and I'm enjoying my new setup a bunch!
amirite said:
In the following threads and others, I'm seeing the first step listed as crucial, and involving flashing this small zip file in order to populate the B slots of the phone:
https://forum.xda-developers.com/moto-x4/how-to/guide-install-android-9-0-pie-gsi-moto-t3833860
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
However, in more recent tutorials as well as the (awesome) videos I've seem floating around from munchy, this step is not shown. In fact, the act of "populating the B slots" now seems tied to flashing a copy of the official firmware in order to prep for custom roms.
I'm a little bit confused about wether the official firmware is now a replacement for this original "copy-partitions-payton.zip" file. Aside from a couple of OP's, I don't see anybody mentioning this file anymore. Also, when instructions are given on "populating the B slots" it seems to now refer to the official firmware flashing process.
Am I getting all of this correct? Is flashing the official firmware a replacement for the step of flashing the copy-partitions-payton.zip file?
I've already unlocked my bootloader.
I really apologize if I'm asking obvious questions, but this is my first android phone in 5 years and I really, REALLY don't want to screw this up. I've had a lot of catching up to do and have been doing a ****-ton of reading in this forum. I think I have the rest of the flashing process figured out... I just want to do the first step right. Thank you so much XDA for being the resource for people like me!!
Click to expand...
Click to collapse
Well, I did not need it. I just went from stock android 9 to LineageOS 16.