Related
I know some hard work goes into making some of these splash screens, but I'd actually prefer to see kernel messages. Just like what I'd see if I were booting Linux up on a PC. If I delete the splash image files, will this break my phone? Or will it just fall back to giving me the kernel print outs?
If there is a recommended sequence of steps required to do this, it really wouldn't hurt to spell them out for me. Thanks!
I would pm a developer.
Im not sure if it can set up like that.
It would look cool though. Keep us posted.
jokeyrhyme said:
I know some hard work goes into making some of these splash screens, but I'd actually prefer to see kernel messages. Just like what I'd see if I were booting Linux up on a PC. If I delete the splash image files, will this break my phone? Or will it just fall back to giving me the kernel print outs?
If there is a recommended sequence of steps required to do this, it really wouldn't hurt to spell them out for me. Thanks!
Click to expand...
Click to collapse
i have tried by editing the init files, but I didnt make it.
someone?
I posted this over in one of the FAQ threads here. There a few encouraging replies, especially regarding the current line of investigation.
The bad news is that Cyanogen himself has declared this difficult so I don't know how much further we'll get.
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
RyanH77 said:
Hi guys... First post here as i seem to be stuck.. My phone is a DHD.
I'm not new to rooting or custom ROM's as i often change the ROM on my phone easily without any problems.. Done it 40-50 times now. Never had a problem. I'm used to the AAHK and know what i'm doing.. However, last night i got fed up of the ROM i had, been having some teething troubles lately so figured i'd put it back to stock and then root again and flash a new ROM, this always solves my problems. Now i always have a few others stored on my SD card incase one won't work (i sometimes get the bad installation, aborted) message and i'm not left without a working ROM, but wanted to unroot and put back to stock so opened the AAHK and proceeded as normal to do so ..
Everything was running fine, writing codes as it should, then when it came to the radio downgrade, it got to a part where it usually moves on to the next stage fairly quickly, but this time it just hung.. I left it a few mins to see if it would carry on, no such luck.. I had no choice but to remove the cable and try again.. Now i'm not a fan of removing cables midway through, but it would have just hung forever so i had no choice..
Anyway.. I can still access the CWM screen and have tried every option to get it to do something, but no matter what i do, i can't get past either the white HTC screen or the Black background with the red triangle.. The files are still there on my SD card obviously, i can access them via a card reader, it's just the phone won't move on as i'm guessing the downgrade being interrupted left it with corrupt data... I would have thought running the AAHK again would have started from scratch and just re-run, but this obviously isn't the case.. Any ideas what to do?
Click to expand...
Click to collapse
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
glevitan said:
Why are you running the Hack Kit being S-OFF? there is no use in doing that. You could have flashed a different rom from recovery after doing a full wipe and everything might have been solved, if it was a software issue.
Click to expand...
Click to collapse
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to get past either screen.
RyanH77 said:
Yes i realise that.. That's how i always flashed new ROM's. i could have a new ROM installed in minutes that way, but the reason i was running the hack kit was to put it back to S-ON and stock RUU.. As far as i was aware you had to run the hack kit to put it back to stock, that's the only way of doing it is it not?..
But that's not the problem, my problem now is, getting the phone to show some signs of wanting to find get past either screen.
Click to expand...
Click to collapse
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
glevitan said:
Are you still S-OFF? then flash recovery again and then a custom rom. Problem solve. If you want to revert to stock, then do that first and the set S-ON the second time...just in case.
Click to expand...
Click to collapse
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
RyanH77 said:
Yes it is still S-OFF, but it won't let me flash anything, run bootloader, access the SD card or i wouldn't have the problem i have..
If i hold volume down and power, i get the usual screen with fastboot, recovery, factory reset, simlock and image crc.. I've tried every one of these apart from the simlock with the same results.. Nothing.. If i select recovery, it flashes the white HTC screen as if it's going to boot, then i get the black phone with the red triangle and it won't go any further.. If i hold volume up and power at that stage, it gives me the apply sdcard:update.zip (which i can't seem to access or just don't have, i'm not sure) and the wipe data/factory reset and cache options..
The only thing it tells me on the screen is E:Can't open /cache/recovery/command
I fear i can't do anything with this phone, even trying to get the hack kit to run is a pain and keeps giving me several errors including the ECHO OFF message. I presume this is because having done the wipe cache and data, i've removed the usb debugging priviliges..
Click to expand...
Click to collapse
You have to flash a recovery in fastboot.....no other way will work.
glevitan said:
You have to flash a recovery in fastboot.....no other way will work.
Click to expand...
Click to collapse
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
RyanH77 said:
How do i do that exactly?? If i select fastboot, it takes me to the next screen which has bootloader, reboot, reboot bootloader and power down, and again, no matter what i press it won't open any external folders or do anything..
Click to expand...
Click to collapse
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
glevitan said:
ok, if it is ok with you, I can connect over teamviewer and do it for you to show you how to do it....send the ID and PASS in a PM.
Click to expand...
Click to collapse
What ID and PASS?? I don't understand? Where would i find them??
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Are you reading what I wrote?? if you are interested, I can connect to your PC via teamviewer (http://www.teamviewer.com) but I need the ID and PASS to do it.
RyanH77 said:
What ID and PASS?? I don't understand? Where would i find them??
Click to expand...
Click to collapse
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
You've misread the situation.. I didn't lie to you about anything, ok, i was unsure of what i'd done, but i certainly didn't ask for help to mislead you and help break my phone. Why would i do that??? I genuinely got stuck with a problem that i didn't know how to get out of.. To be honest i've never had a problem with it before and didn't realise you had to know every single piece of info about it, most of which you forget whilst trying to sort it anyway, and i can't remember if it was flashed previously with a stock ROM or not, but what you mentioned sounded familiar which is why i said i think it might have been, but i can't be 100% certain on that..
I feel bad that you saw it as misleading, as i didn't feel i had been, and that certainly wasn't my intention.. But even though you are unwilling to help me again, i thank you very much for the help you gave me, without you it would still be in a useless state. Thankfully, i have managed to get it working perfectly again and will be more careful in future..
glevitan said:
Ryan, from now on, know that if you lie on what you did your phone to someone trying to help you is the worst thing ever. Not only because it won't help to fix it but also because I could also have scr*wed your device by doing some flashing on a messed bootloader.
Lying is the worst strategy ever....I am done. You won't get any help from me anymore. Congrats.
Click to expand...
Click to collapse
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
-SmOgER said:
What's wrong with you dude?
If someone doesn't have a knowledge on something (misunderstoods, etc..) it doesn't mean hes lying, lol.
Click to expand...
Click to collapse
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
glevitan said:
Maybe you don´t have a clue on what happened. What's up with me? I will tell you what is going on...i spend many hours of my life helping people in here and in the Hack Kit IRC Support Channel for free, I do it because I enjoy it and don't expect anything in return.
But the worst thing ever is to come accross someone that lies about what he did to his phone. I have been around this site for about 2 years now and never made a brick, do you know why? because I always make sure to follow instructions and ask people what they did in order to provide the best fix, if possible.
When you spend and hour trying to figure out what is going on and trying to flash something and then find out that a froyo RUU might have been flashed (perhaps, I don´t know, not sure...WTF???) and what you did might have scr*wed his phone, it really makes me angry and feel cheated.
To sum up, my time...my decision...maybe you can help him yourself instead of questioning me.
Click to expand...
Click to collapse
Like SmOgER said before you Glevitan, i wasn't lying, you just got annoyed with me because i didn't give you 100% of the info you needed, and the only reason for that was because i didn't know it!! When you think you're phone is playing up, you try various ways to get it right again, i'm sorry i don't keep track of every little step i did and i'm sorry this displeased you. But a liar i am not.. The term more appropriate would be clueless!!
You have to accept that us newbies just don't know anywhere near as much about these phones and how they work as you do.. It doesn't mean i lied.. What you see as a misrepresentation of facts doesn't mean i am a liar, it just means i didn't give you the info you wanted, simply because i didn't know it, not that i was withholding it on purpose, THAT would have been bad!!
I am no expert like you, i just root and ROM like most people and hope that it goes right...
Like i said before, i really appreciate the time you took to help me and didn't go unnoticed, and it's great that you help people like me for free, but maybe you should take it a bit easier on the newbies if they're not so expert.. My 1st post asking for help and i already feel like i'm not welcome anymore.. That's pretty bad for such a big community!!
SmOgER.. At least YOU understood where i was coming from..
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
bananagranola said:
1. Flashing a Froyo RUU is an important stop on the quick path to bricking your phone, and that warning is splashed all over AAHK and other documentation. That's why glevitan is so upset about not being told of the possibility that you might have done it: it's very bad, and users should know that it's very bad, and it wastes a lot of time.
2. Not knowing what you're doing and messing with your phone, and then not keeping track of what you're doing, is extremely unwise. When helping out on XDA, I personally don't expect everyone to know everything, but taking basic precautions really does seem like common sense.
3. Next time, read similar threads that came before you and ask the community. For example: I have X problem. I have researched and found Y and Z thread links with similar symptoms. I am considering trying what A suggested in Y. Is that the wisest course of action? Then you show that you have done your part in solving your own problem, and the community will respect that, even if you're way off base.
Obviously, I personally wasn't there on teamviewer, so I have no idea about the clueless v. lying thing.
Click to expand...
Click to collapse
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Whatever happened doesn't matter anymore. Lesson learned.
You seem like a nice guy. Let's back on topic.
Is the issue solved or not?
Try to state what is the current issue. What was the state of the phone when it was working. What happened or what were you trying to do when it got messed up. What have you tried so far. Etc, etc, etc. The more the info the better.
Edit: Nevermind. You *******, you flashed a froyo hboot on your HTC Inspire/DHD after we’ve warned NOT to for over a year. Here’s the fix:
Sent from a dream.
RyanH77 said:
Yes i understand what you're saying, and i appreciate most of it. However, it's not often practical or even possible in some cases to write down or note everything you do in a documented fashion.. And like you might have previously missed, i have flashed various ROM's 40-50 times, and the AAHK has worked perfectly for me everytime except the last where it took it upon itself to just freeze on me, it was a computer issue, not a human error.. Also, why would reflashing a Froyo RUU to a phone that was originally shipped as a Froyo unit cause any problems??
I don't understand that part..
One final note, i did have a look through similar threads, but there are so may threads with similar symptoms that it's hard to sift through them all for a definitive answer, and even when you do read them, only one or two parts might be relevant, if any.. So it's quicker to come straight out and ask rather than waste hours trawling through them all to no avail i think.
Click to expand...
Click to collapse
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
glevitan said:
It is not about if you are an expert or not...I am not, belive me. But I am wise enough to read and try to learn. Doing things like a monkey will not excuse you.
If you don't understand, maybe it is time for you to buy an Iphone. Hacking is not for the lazy b*stards who don't even know what they do. And belive me, your story is hard to belive, running the Hack Kit with a custom rom is not possible...you should have got stuck, that is how it works.
YOUR PHONE....YOUR PROBLEM...I don't give a penny for it.
Click to expand...
Click to collapse
I wouldn't be seen dead with an iPhone.. I hate Apple and Apple products for that specific reason. They don't give the freedom of open source and don't allow real control. But i will be more careful in future and learn from my mistakes.. However, i'm not a lazy bastard hacker as you so put it, and i don't care for the accusation of being one either, please be careful what you say in future as statements like that are completely uncalled for ..
I understand you are somewhat unhappy with me, but please don't resort to slating me. I wouldn't do the same to you if you were wrong.
And yes Teichopsia.. I am a nice guy, thank you for noticing.. I realise now i made a mistake and i just got stuck, but the phone is now running absolutely flawlessly thank you..
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.