im still noob on nexus s, i just would like to ask if there is a possibility to permanently brick a nexus s?
Sure, why not. But you gotta be doing a lot stuff wrong before you hard brick the NxS.
As long as your careful, no. No full brick as been reported with.nexus s yet.
snandlal said:
As long as your careful, no. No full brick as been reported with.nexus s yet.
Click to expand...
Click to collapse
Actually some ppl bricked their devices by destroying the EFS folder, resulting in no IMEI. You can still fix this with a hardware mod, but not everyone is capable of doing that nor has access to it (and it's illegal mostlikely).
rentaric said:
Actually some ppl bricked their devices by destroying the EFS folder, resulting in no IMEI. You can still fix this with a hardware mod, but not everyone is capable of doing that nor has access to it (and it's illegal mostlikely).
Click to expand...
Click to collapse
is the hardware mod you're talking about is something like with hardware tool like jtag, or etc? so if this happened to me, i can't fix it alone with the use of some software tool, i need to send it in a repair shop?
sorry for these irritating noob questions,
maybe tomorrow i will root my nexus s with 1click root by borky_16, if i failed to install it, what kind of brick will i be getting?
You have a developer phone with a unlockable bootloader. Learn how to do it the proper way and not some 1click nonsense for a nexus/GED device.
To be honest if you can't install the sdk and follow the very simple instructions how to root/flash/nandroid etc you really have no business with su privileges on any *nix machine.
albundy2010 said:
You have a developer phone with a unlockable bootloader. Learn how to do it the proper way and not some 1click nonsense for a nexus/GED device.
To be honest if you can't install the sdk and follow the very simple instructions how to root/flash/nandroid etc you really have no business with su privileges on any *nix machine.
Click to expand...
Click to collapse
Exactly. Read the directions and you'll be fine It is veryyyy easy.
zhane0513 said:
is the hardware mod you're talking about is something like with hardware tool like jtag, or etc? so if this happened to me, i can't fix it alone with the use of some software tool, i need to send it in a repair shop?
Click to expand...
Click to collapse
bro, im from the philippines too, my nexus s is just stuck at the google logo, i brought it to the repair shop already and they cant fix it, they said whenever they try to unlock the bootloader it keeps hanging up. i really dont know what else to do, the guy there told me to have my nexus s jtag'd but im not sure of leaving my phone there.
guys, what should i do?
tnx for your replies dudes...i will try my best to learn about nexus world anyway, i have also an old android phone which i was able to root install custom roms/kernels/tweaks/etc it would be a good prior knowledge though,
ouch...what did u do to made it into brick? try sending it to samsung shops, even though warranty is voided, they can still repair your phone with service fee i think
if you dont know what you are doing is,it might be.
i know a little bit cause i install mods/roms/kernels/tweaks to my previous android phone...just asking to be more safer
zhane0513 said:
ouch...what did u do to made it into brick? try sending it to samsung shops, even though warranty is voided, they can still repair your phone with service fee i think
Click to expand...
Click to collapse
it was lowbatt then it shutdown, after i charged it, it never booted up till the x animation its just stuck at the google logo.. hassle, i bought this phone from india so i dont think samsung shops here in manila will even try to fix it.. i gave it to a really well known technician he said he was gonna jtag it.. i just hope he can fix my nexus s, i just had it for 3months.
can you brick the phone by undervolting too much ?
or you can always get into fastboot recovery and flash a stock rom ? (or change the uv settings via ADB)
mine is completely bricked, i sent it back to samsung india, cause im based in the philippines. after my technician tried to use odin and he even jtag'd it now it wont boot up, its just dead. i hope samsung india fixes it for free cause its still locked.
Thing I should explain something. Bricks are forever. That's what brick means. That being said, you can as some call it "soft" brick and recover. A true brick, becomes just that, a "brick". The device will never run again from anything the end user can do.
Sent from my Nexus S 4G
Now bricks are not forever...
http://forum.xda-developers.com/showthread.php?t=1236273
Sent from my unbrickable cappy *bam*
Related
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char
Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
since HTC released the kernel code, I thought it would be easier to revert back to enterily stock
Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....
Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.
Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?
socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!
It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.
I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?
maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?
potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL
I was new to the whole world of android and was unaware of the Galaxy Fit's issue with ROM Manager, i installed it, flashed the recovery and bricked my phone, i was devastated, i took my phone to the shop i got it from and they took it in, for 7 days i was full of worries and couldn't think about anything except will they fix my phone? Well, they did, the fixed it, at the bottom of the diagnostic report it simply read "Phone is refusing to turn on. Replaced motherboard."
So, you will think 2 things once you have read this:
a) Your lieing !!!
b) What about the ROOT VOIDS YOUR WARRANTY thing !?
Answer to A: Im not.
Answer to B: Easy, if you read the warning about ROM Manager you will notice that it corrupts your whole motherboard leading the specialists to not be able to make a full diagnostic, basically, they cant access the system, data, cache, and most importantly, cant access the BOOTLOADER, why? CAUSE ITS CORRUPTED!
I made this thread because i dont want people to worry about their phone if its gona get fixed or not if they bricked it this way, those 7 days lasted like an eternity for me.
Thank You !
Now, just to be clear, rootin and custom roms DO void your warranty, but not if there is no evidence to them, examples: Unroot, stock rom, corrupted motherboard.
It's always advisable to acquire proper knowledge beforehand.
Don't use Rom Manager ever. Use Odin to flash recovery. Browse our XDA for more...
Sent Via XDA™ Premium
I've heard of people damaging their phones on purpose just to make sure that the manufacturer doesn't come to understand that it's been rooted. I guess it's much easier with root access xD
The warranty thing is hardly a problem now, I guess
I have a LG Mach (AKA Cayenne, LS860) LG Apparently algo named the LU3000 "Mach" as well for w/e reason. There is a distinct lack of ANYbody developing for this phone. I would like to take on doing it myself, but I am unclear on how to start. I managed after about a week to root the stock rom, but I can't find any recoveries for it. How should I go about this?
I understand that this is a very in depth question and for most, it would be too much to tackle. However, I have a background in C++ and Visual Basic (though I am a little rusty). Any direction would be nice and I am willing and capable of learning anything necessary to accomplish this.
Thanks!
Well this is a combination of bump / information. Since there is a lack of information regarding this phone out here, I figured I would share the method I used to root this phone. It works on the stock 4.0.4 rom.
http://forum.xda-developers.com/showthread.php?t=1886460
I was thinking about compiling TWRP for this phone myself, but I would like input from everyone if CWM would be a better choice? Input welcome
CorySCline said:
Well this is a combination of bump / information. Since there is a lack of information regarding this phone out here, I figured I would share the method I used to root this phone. It works on the stock 4.0.4 rom.
http://forum.xda-developers.com/showthread.php?t=1886460
I was thinking about compiling TWRP for this phone myself, but I would like input from everyone if CWM would be a better choice? Input welcome
Click to expand...
Click to collapse
I just won this phone, and I'm putting the term LG MACH ROOT/LG MACH BOOTLOADER in this thread so people can find it via google.
There is pretty much no developer love for this phone...
I don't care which way you do it. Personally I prefer TWRP because of it's touch controls.
Mgamerz said:
I just won this phone, and I'm putting the term LG MACH ROOT/LG MACH BOOTLOADER in this thread so people can find it via google.
There is pretty much no developer love for this phone...
I don't care which way you do it. Personally I prefer TWRP because of it's touch controls.
Click to expand...
Click to collapse
Well, it looks like its up to me and you:
Im going to compile TWRP tonight for it, and if all goes well, I will create a new thread with the rooting method and recovery explained. However, know that you will officially be person #2 to use this recovery image. All warnings and potential problems will apply.
Up for some fun?
I haven't got the phone yet actually. Briefmobile informed that I won and that sprint will ship it. I don't know anything more than that :/ I hope soon. It'd be fun to mess with the phone while my college break is going on still.
Sorry about the really slow replies. I should subscribe so that tapatalk notifies me.
I don't know when it will get here :/
But since you have it, do you know if the bootloader is unlocked/unlockable? Google is surprisingly of little use with this phone. I'd love to dink around with this phone since it's not my primary one (and I can't use cellular services on it)
Mgamerz said:
I haven't got the phone yet actually. Briefmobile informed that I won and that sprint will ship it. I don't know anything more than that :/ I hope soon. It'd be fun to mess with the phone while my college break is going on still.
Sorry about the really slow replies. I should subscribe so that tapatalk notifies me.
I don't know when it will get here :/
But since you have it, do you know if the bootloader is unlocked/unlockable? Google is surprisingly of little use with this phone. I'd love to dink around with this phone since it's not my primary one (and I can't use cellular services on it)
Click to expand...
Click to collapse
All good, it takes time to develop these things anyways. I should have a stable TWRP build within a few days, and a CyanogenMod 10.1 (Android 4.2) build complete in the next couple of weeks.
The bootloader is something I am going to tackle tonight. As you can tell, there is zero documentation on the web for this device. In fact, it received more attention when it was a concept than it does now. So for now, I have no answer on the bootloader. I hope so, or all my work is useless lol. However, root is obtained at a bare minimum
Anyone out there that comes across this thread that wants to find information on modding this phone, PLEASE post your interest here. Trust me, you won't find any other resources.
lg locked bootloaders
I have the lg motion, I don't know how close it is to the mach but I've been following a thread for several months that has been trying to figure out a workaround for the locked boot loader. Google all things root guide for lg motion and you might be able to find a decent starting point for your phones maybe even help them figure out the motion
Ok, well I think, for now at least, root is all we are getting . I have managed to develop and compile ClockworkMod Recovery TeamWin Recovery, and Cyanogenmod 10.1 for it, but realized after all that work that the bootloader is not only locked, but also signed with a digitally encrypted key. Basically in laymans terms: We are ****ed. So, if anybody manages to shmooze either Sprint or LG out of these unlock codes, let me know and I'll provide everything else. Otherwise, anything I have made will brick every LS860 it goes on. Sorry guys.
Oh boy is like Motorola all over again... So no flashing recoveries even?
Sent from my Galaxy Nexus using Tapatalk 2
Hey!
Sent from my LG-LS860 using Tapatalk 2
Mgamerz said:
Oh boy is like Motorola all over again... So no flashing recoveries even?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thats correct. At least from my understanding. I could be wrong, but without the ability to unlock the bootloader i dont want to try flashing recovery. Too risky for me. Ill give anyone who wants to try my twrp build but i wont accept any repercussion for it doing anythin negative
Give me your twrp build then
I just rooted it. Was super easy.
Tried adb reboot bootloader. Did nothing. Tried adb reboot recovery. Recovered the device. Can't seem to figure out a way to have it download software. (like nvflash) Wonder if there's a special cable...
Sent from my LG-LS860 using Tapatalk 2
So I already bricked two, lol. Not going for a third. I really wanna root this phone. I went as far as getting the firmware which is a cab file. But then I guess you have to convert that to a kdz file. Then decrypt the kdz file. Well it appears you need to be an LG Service tech to use the program. Was hoping there was work around for all this,
Sent from my LG-LS860 using xda app-developers app
LG_Mach said:
So I already bricked two, lol. Not going for a third. I really wanna root this phone. I went as far as getting the firmware which is a cab file. But then I guess you have to convert that to a kdz file. Then decrypt the kdz file. Well it appears you need to be an LG Service tech to use the program. Was hoping there was work around for all this,
Sent from my LG-LS860 using xda app-developers app
Click to expand...
Click to collapse
I rooted it, it was easy using the sony tool that does the adb backup remount bug, but that's as far as I got. I uninstalled a bunch of crap off of the system partition and its a lot faster now, too bad I can't get that activation screen to go away.
Just pulled the newest OTA. I found it in /cache. I tried to get the URL but instead I made it so it no longer sees there's an update... I have the zip file however, and inside of it there is patches to just about everything in system, and updates to magazines, chrome, and LGBookmarksProvider.
There's also a command to install a recovery image:
#!/system/bin/sh
/sbin/write_recovery /dev/block/platform/msm_sdcc.1/by-name/recovery
Not sure if it's a good idea to flash that... forgot that it's still locked bootloader
EDIT: Finally figured out download mode... I just held all the buttons down when starting it and voila, it's there. I also hear you can use the LG Software update tool to flash back to stock, so we might finally have root that's safe
Does anyone have the BooksTablet.apk found in /system/app? I'm not sure why but it won't install the update cause the sha1 of that file fails I don't know where to find it.
Dont let this thread die! I noticed there was no dedicated forum for the LS860 development, I really enjoy this phone and would love some level of development for it. I can help as much as I am able.
jfm567 said:
Dont let this thread die! I noticed there was no dedicated forum for the LS860 development, I really enjoy this phone and would love some level of development for it. I can help as much as I am able.
Click to expand...
Click to collapse
Can someone rip me their BooksTablet.apk and BooksTablet.odex from their LS860 and PM me a link to it? I really am pissed off at the update prompt (I'm not sure why it's not working, I haven't touched it and I made sure I backed everything up... It won't validate BooksTablet.apk) I'm on the stock original version of the software ZV6 or something... not the ZV7.
I really don't want to go into sprint that much, though I might have to do that soon.
Edit: Just called sprint. They won't do anything for me and I'm not going to pay money for someone to reflash my phone. It's pretty ridiculous how factory images for devices aren't released. You know how many issues this would solve? That's why nexus devices are great. They're practically unbrickable.
Hey guys, try posting the mach in here so maybe it can get a forum for it.... And possibly some development.
http://forum.xda-developers.com/showthread.php?t=1660354
Hi, I have LG Mach (LG LS860) - the Root MANY ANDROID! [Upd: 17.04.2013] Sony method worked with software version ZV6, but I have purchased a new LG Mach with ROM version ZV7 (an update from Feb 20) - and this method runs but does not result in root - how can I roll this software version back or else get root in an alternative manner? - please help!
Hi!
Dont know if this is posted in the correct thread, but I'll try anywayz.
I have a LG g2, and when I accepted a software update the phone got stuck in the clockworkmod recovery-something.
Tried to click on factory reset etc, but nothing works. It just loops back to the same place.
The company that sold the phone say they will not repair it because clockworkmod is unauthorised software and the warranty does not apply.
The problem is, I have never herd of clockworkmod in my life before this happened. Can clockworkmod install itself without me doing anything?
I checked my backupinfo on apps installed from google play and none of them said clockworkmod.
Is it possible to find out when a program was installed and how it was installed?
If anyone has any idea, I would be very greatfull.
dirtsa said:
Hi!
Dont know if this is posted in the correct thread, but I'll try anywayz.
I have a LG g2, and when I accepted a software update the phone got stuck in the clockworkmod recovery-something.
Tried to click on factory reset etc, but nothing works. It just loops back to the same place.
The company that sold the phone say they will not repair it because clockworkmod is unauthorised software and the warranty does not apply.
The problem is, I have never herd of clockworkmod in my life before this happened. Can clockworkmod install itself without me doing anything?
I checked my backupinfo on apps installed from google play and none of them said clockworkmod.
Is it possible to find out when a program was installed and how it was installed?
If anyone has any idea, I would be very greatfull.
Click to expand...
Click to collapse
Did you buy this phone brand new? It looks like the previous owner installed CWM Recovery on it. You can flash a custom firmware for your LG G2 from CWM or if you want to return to stock firmware, follow the steps from here: droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
As for warranty, this is not covered, sorry.
Also, CWM CANNOT install itself. Either you or someone else installed it. You usually need root to install or you need to flash it. So it can't happen by accident. You can't install it like a normal app from the play store.
andreiav said:
Did you buy this phone brand new? It looks like the previous owner installed CWM Recovery on it. You can flash a custom firmware for your LG G2 from CWM or if you want to return to stock firmware, follow the steps from here: droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
As for warranty, this is not covered, sorry.
Also, CWM CANNOT install itself. Either you or someone else installed it. You usually need root to install or you need to flash it. So it can't happen by accident. You can't install it like a normal app from the play store.
Click to expand...
Click to collapse
Hi, and thank you so much for the answer.
I bought the phone brand new from the store. I looked at the link, and thank you for that - I don't think I am capable of doing such a prosedure myself - but maybe I can send it to a mobile-workshop and they can do it for me. Thank you so much for that as well.
I don't understand how this program got in to my phone, they said that it was "rooted with unauthorised software" - I have no idea what rooting means. I am going to try to get to the bottom of this and find out how this program got into my phone in the first place.
dirtsa said:
Hi, and thank you so much for the answer.
I bought the phone brand new from the store. I looked at the link, and thank you for that - I don't think I am capable of doing such a prosedure myself - but maybe I can send it to a mobile-workshop and they can do it for me. Thank you so much for that as well.
I don't understand how this program got in to my phone, they said that it was "rooted with unauthorised software" - I have no idea what rooting means. I am going to try to get to the bottom of this and find out how this program got into my phone in the first place.
Click to expand...
Click to collapse
You are very welcome. If you do not know what rooting is, then clearly it wasn't you who did it. Your phone gut stuck because of the custom recovery on your phone. Updates can only work with stock (original) recovery.
Was the phone sealed? (the box, the battery...?) It really sounds like somebody from that store ripped you off with a modified phone.
If you can't prove it, then take it to a mobile service. I'm sure they can handle it. Sorry for your warranty though..
Good luck with it.
Thanks again for the answer. I talked to a company who offers mobile workshop. They said it is no way of finding out who "rooted" the phone. I don't know why they keep talking about the rooting. I sent an email and asked if it was possible to find out when and how a program was installed on my phone. Do you know if it is possible to find out primarily WHEN clockworkmod was intalled, and secondary how it was installed?
On computers you can see when a program was installed so I thought maybe you could do that with mobile phones as well?
Sorry for all this stupid questions, but I am quite annoyed because I bought the phone from the biggest telephone company in my country, and now it has become my mission in life to prove that I didn't do this myself
Best Regards
dirtsa said:
Thanks again for the answer. I talked to a company who offers mobile workshop. They said it is no way of finding out who "rooted" the phone. I don't know why they keep talking about the rooting. I sent an email and asked if it was possible to find out when and how a program was installed on my phone. Do you know if it is possible to find out primarily WHEN clockworkmod was intalled, and secondary how it was installed?
On computers you can see when a program was installed so I thought maybe you could do that with mobile phones as well?
Sorry for all this stupid questions, but I am quite annoyed because I bought the phone from the biggest telephone company in my country, and now it has become my mission in life to prove that I didn't do this myself
Best Regards
Click to expand...
Click to collapse
Unfortunately, I don't think you can find out when CWM recovery was installed, or when the phone was rooted.
They keep talking about rooting because your phone is most likely rooted. Rooted means having a piece of software installed on the phone that gives you full access. And you can then modify anything on the phone, including system files. It's like having Administrator rights on Windows let's say.
Good luck with your phone
Hello I'm waiting to purchase op6 t never owned OP phone. Wondering if I screw up trying unlock bootloader, rooting etc is it a easy fix? Just asking ahead of time and reading thru forums. Any tips greatly appreciated.
lilmeanz said:
Hello I'm waiting to purchase op6 t never owned OP phone. Wondering if I screw up trying unlock bootloader, rooting etc is it a easy fix? Just asking ahead of time and reading thru forums. Any tips greatly appreciated.
Click to expand...
Click to collapse
Honest answer is wait for the 6t and see if someone figures it out.
If your device is ever soft bricked but you can still access TWRP - you can sideload OOS using fastboot "adb sideload *rom name.zip*. If sideloading fails, you can "adb push *rom name.zip* /data/media/0".
It's next to impossible to brick the oneplus 6 however.... NEVER EVER relock the bootloader with a custom recovery that's the only way I know of which WILL brick your phone.
Despite what you may have read, this is an easy phone to root and mod, it just works differently from other phones, particularly non-A/B phones. This is what has a lot of people salty and frustrated because they don't want to change from the way they think things "should" work.
I don't know of anyone here who has hard-bricked. There is an unbrick tool that works well.
daleski75 said:
It's next to impossible to brick the oneplus 6 however.... NEVER EVER relock the bootloader with a custom recovery that's the only way I know of which WILL brick your phone.
Click to expand...
Click to collapse
also this wont brick your phone. snapdragons are unbrickable.